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:
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
CouchDB Riak 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)