Exclusive updates on:

MongoDB @ SourceForge
Recorded at:

by Mark Ramm on Aug 26, 2010 | NOTICE: The next QCon is in San Francisco Nov 7-11, 2016. Join us!

View Presentation

Download
MP3
|
Slides
|
Android app

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.

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.

Related Editorial

Getting started with Elasticsearch and Node.js

Is PostgreSQL Your Next JSON Database

Getting Started with ScyllaDB, Drop-in Replacement for Cassandra

Architecture for a Scalable Enterprise Content Repository

Using GraphQL with MongoDB

Related Sponsor

Compose makes it simple to deploy production-ready databases in minutes in the cloud or on your own servers.

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Community comments

MongoDB (not) faster than CouchDB by Thomas Mueller Posted

Confusion by Stephen Devonald Posted

MongoDB (not) faster than CouchDB by Thomas Mueller

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

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.