We do most of our development in Django, so Postgres is a natural fit. Every tool has its sweet spots, so you should use the tool that best fits the task.
For instance, Postgres is great for highly structured data (say, photos on a website). Riak shines when your data flexs more & you have a lot of it (say an activity stream).
Riak is distributed (it automatically shards data on many servers). CouchDB runs on a single server, although it can easily have as many mirrors as needed.
Also, Riak features an integrated full-text search engine.
Another key/value store?
I'm sure it has its own specific advantages and disadvantages which make it different from all the others.
Still, there's a lot of those popping up lately...
9 comments
[ 2.4 ms ] story [ 32.5 ms ] thread"We're not about to drop PostgreSQL as our primary data storage layer, but Riak seems to make a great complimentary datastore . . . "
For instance, Postgres is great for highly structured data (say, photos on a website). Riak shines when your data flexs more & you have a lot of it (say an activity stream).
Why no mention of CouchDB and how Riak differs?
In short, Riak wins out to me against all three:
* Faster than Couch & easier clustering * Better data integrity than Mongo * Less conceptual overhead & simpler code than Cassandra
Also, Riak features an integrated full-text search engine.