Recommendation for an in-memory database

database nosql rdbms in-memory-database
vonPetrushev picture vonPetrushev · Mar 6, 2011 · Viewed 13.4k times · Source

I would like to remove sql dependency of small chunks of data that I load on (almost) each request on a web application. Most of the data is key-value/document structured, but a relational solution is not excluded. The data is not too big so I want to keep it in memory for higher availability.

What solution would you recommend?

Answer

Nishant picture Nishant · Mar 6, 2011

The simplest and most widely used in-memory Key-value storage is MemcacheD. The introduction page re-iterates what you are asking for:

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

The client list is impressive. It's been for a long time. Good documentation. It has API for almost every programming language. Horizontal scaling is pretty simple. As my experience goes Memcached is good.

You may also want to look into MemBase.

Related questions

NoSql vs Relational database

Recently NoSQL has gained immense popularity. What are the advantages of NoSQL over traditional RDBMS?

Read More
When NOT to use Cassandra?

There has been a lot of talk related to Cassandra lately. Twitter, Digg, Facebook, etc all use it. When does it make sense to: use Cassandra, not use Cassandra, and use a RDMS instead of Cassandra.

Read More
What's the difference between NoSQL and a Column-Oriented database?

The more I read about NoSQL, the more it begins to sound like a column oriented database to me. What's the difference between NoSQL (e.g. CouchDB, Cassandra, MongoDB) and a column oriented database (e.g. Vertica, MonetDB)?

Read More