From CouchDB to Riak at Linkfluence
We were already aware of Riak before we started using CouchDB, but we weren’t sure about trusting a new product at this point, so we decided, after some benchmark, to go for CouchDB.
After the first couple of months, it was obvious that this was a bad choice.
Our main problems with CouchDB is scalability, versioning and stability.
I am wondering how using BigCouch would have addressed Linkfluence requirements:
- easy to replicate (CouchDB already has replication)
- REST interface (CouchDB has that)
- master/slave (CouchDB replication is peer-to-peer)
- sharding (BigCouch was created to make CouchDB horizontally scalable)
and the stability/maintenance issues.
The article also gives an overview of Linkfluence polyglot persistence architecture:
- PostgreSQL: some indexes on documents’ ID
- MongoDB: store tweets relationships and some indexes
-
CouchDBRiak for content and metadata - Redis for caching
- Solr for search indexes
- ElasticSearch for secondary indexes
You might also enjoy some of the comments on the Hacker News thread.
Original title and link: From CouchDB to Riak at Linkfluence (NoSQL databases © myNoSQL)
via: http://labs.linkfluence.net/nosql/2011/03/07/moving_from_couchdb_to_riak.html
