MongoDB and foursquare
There is a case-study for mongoDB at foursquare up on 10gen's site. Mainly the usual stuff, viz. AutoSharding, GeoIndexing, Replica Sets, and Document Model.
Nothing in the case study actually screams out "Yes! This is why they should have used MongoDB"(over BigCouch for example), which is pretty funny, since one of MongoDB's big differentiators (high write throughput) would have been a key feature.
Note: FWIW, the high write throughput comes with the potential for data loss, but thats not really an issue for foursquare (if your checkin doesnt work, just do it again...).
Another Note: The idea that a database doesn't guarantee the writes and can occasionally lose data is, of course, interesting :-)
Nothing in the case study actually screams out "Yes! This is why they should have used MongoDB"(over BigCouch for example), which is pretty funny, since one of MongoDB's big differentiators (high write throughput) would have been a key feature.
Note: FWIW, the high write throughput comes with the potential for data loss, but thats not really an issue for foursquare (if your checkin doesnt work, just do it again...).
Another Note: The idea that a database doesn't guarantee the writes and can occasionally lose data is, of course, interesting :-)
Comments