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



scaling: All content tagged as scaling in NoSQL databases and polyglot persistence

Handling Growth With Postgres: 5 Tips From Instagram

As we’ve scaled Instagram to an ever-growing number of active users, Postgres has continued to be our solid foundation and the canonical data storage for most of the data created by our users. While less than a year ago, we blogged about how we “stored a lot of data” at Instagram at 90 likes per second, we’re now pushing over 10,000 likes per second at peak—and our fundamental storage technology hasn’t changed.

I only knew about the fifth one and I think the 2 tips about partial and functional indexes being extremely useful in general.

Original title and link: Handling Growth With Postgres: 5 Tips From Instagram (NoSQL database©myNoSQL)


The Key Technical Challenge of Cloud Computing

Adrian Cockcroft[1]:

The key challenge is to get into the same mind-set as the Google’s of this world, the availability and robustness of your apps and services has to be designed into your software architecture, you have to assume that the hardware and underlying services are ephemeral, unreliable and may be broken or unavailable at any point, and that the other tenants in the multi-tenant public cloud will add random congestion and variance. In reality you always had this problem at scale, even with the most reliable hardware, so cloud ready architecture is about taking the patterns you have to use at large scale, and using them at a smaller scale to leverage the lowest cost infrastructure.

  1. Adrian Cockcroft: Cloud Architect at Netflix, @adrianco  

Original title and link: The Key Technical Challenge of Cloud Computing (NoSQL databases © myNoSQL)


What is Riak?

From Basho’s blog:

Riak is:

  • A Database
  • A Data Store
  • A key/value store
  • Used by Fortune 100 Companies
  • Used by startups
  • A “NoSQL” database
  • Schemaless and data-type agnostic
  • Written (primarily) in Erlang
  • As distributed as you want and need it to be
  • Scalable
  • Pronounced “REE-ack”
  • Not the best fit for every project and application
  • And much, much more…

So far I’ve heard only about Riak and Mozilla, Riak at, and this atypical Riak usage for a church kiosks, but no mentions of Fortune 100 company names. Anyone knows who are they referring to?

Update: please check the comment thread for more details. It looks like the Fortune 100 company Basho is referring to is Comcast.

Original title and link for this post: What is Riak? (published on the NoSQL blog: myNoSQL)