NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



MongoDB in Numbers: Foursquare, Wordnik, Disney

Derrick Harris:

If you’re wondering what kind of performance and scalability requirements forced these companies to MongoDB, and then to customize it so heavily, here are some statistics:

  • Foursquare:
    • 15 million users;
    • 8 production MongoDB clusters;
    • 8 shards of user data;
    • 12 shards of check-in data;
    • ~250 updates per second on user database, with maximum output of 46 MBps;
    • ~80 check-ins per second on check-in database, with maximum output of 45 MBps;
    • up to 2,500 HTTP queries per second.
  • Wordnik:
    • Tens of billions of documents with more always being added;
    • more than 20 million REST API calls per day;
    • mapping layer supports 35,000 records per second.
  • Disney:
    • More than 1,400 MongoDB instances (although “your eyes start watering after 30,” Stevens said);
    • adding new instances every day, via a custom-built self-service portal, to test, stage and host new games.

Add to these Viber Media numbers:

  • 30 million plus registered mobile users
  • 18 million active users talking 11 million minutes every day

I have an exclusive interview with Viber Media people queued up for the next days.

Original title and link: MongoDB in Numbers: Foursquare, Wordnik, Disney (NoSQL database©myNoSQL)