InfoQ Homepage Presentations MongoDB @ SourceForge
MongoDB @ SourceForge
59:10
Summary
Mark Ramm tells the story of why SourceForge needed to redesigned its site, why they chose MongoDB, how it compared to other possible solutions, the problems encountered, how they fixed them, and overall lessons learned. Ramm also responds to various questions coming from the audience.
Bio
Mark Ramm is an web developer who's interested in everything from making everyday development easier to scalability and high traffic websites. He's the BDFL of TurboGears 2, and is leading the charge to modernize the tech stack at GeekNet for sourceforge.org.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Aug 26, 2010
-
-
What is Distributed SQL? Scale, Resilience, and Data Locality for Modern Applications (By O'Reilly)
Related Sponsored Content
-
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/2c3c7563-ee6e-4d0c-ade6-a8fa95fa3dca/CockroachLabsLogRSB-1645612933861.png)
Community comments
MongoDB (not) faster than CouchDB
by Thomas Mueller,
Confusion
by Stephen Devonald,
MongoDB (not) faster than CouchDB
by Thomas Mueller,
Your message is awaiting moderation. Thank you for participating in the discussion.
If I understood correctly, the presentation says that writing to CouchDB is much slower than writing to MongoDB. The following blog post discusses this: www.rethinkdb.com/blog/2010/07/the-benchmark-yo... (I'm not related to those projects)
Confusion
by Stephen Devonald,
Your message is awaiting moderation. Thank you for participating in the discussion.
Mark is clearly an excellent protagonist of current improvements in technology, and I would accept that the 6 week timescale for thw project imposed a tight deadline (one that he may havw negotiated or refused!).
It is unclear whether having chosen MongoDB, he tried to annexe some of their technical expertise as consultants on the project. With so many unknowns in the project, I feel he should have attempted to involve supplier expertise more - especially once the technolofy suppliers were chosen.