Viber Replaces MongoDB with Couchbase

My eyes hurt from reading so much PRese. Look, every organization from from Solution A to Solution B in due course-- and that is a PR Story. But for it to be useful programmers, there has to be some amount of quantitative data to support the decision ;a video embed doesn't count. Surely Couchbase folks can do better than this to catch our attention.

I don&#x27;t entirely know what Viber does, but given how very different MongoDB and Couchbase are, I think they made a terrible choice of using MongoDB in the first place. You can&#x27;t fault MongoDB for that. Viber announcing this change is more of an admission that their architects&#x2F;engineers made a bad choice than it is a slight against MongoDB.<p>Also, I don&#x27;t like MongoDB very much and almost always find another more suitable database (both SQL and NoSQL) for the projects that I have worked on.

Is anyone else using Couchbase? I&#x27;m evaluating it for a project with a mobile component and Couchbase Mobile with its automatic syncing seems like a great solution. Would love to hear peoples thoughts.

In related news, Viber manages to bootstrap their startup all the way to billions of messages and talking minutes per month with MongoDB.<p>Sounds like Mongo was a great choice and they&#x27;re just growing up.

Couchbase and MongoDB are both excellent databases and have their place. I work with a MongoDB implementation that has over 12.75 billion records, adds over a billion records per year, and runs in a high availability, high read environment. <a href="http://jaihirsch.github.io/straw-in-a-haystack//mongodb/2014/01/06/mongodb-legacy-migration/" rel="nofollow">http:&#x2F;&#x2F;jaihirsch.github.io&#x2F;straw-in-a-haystack&#x2F;&#x2F;mongodb&#x2F;2014...</a><p>Know your problem domain, do your research, benchmark, test multiple solutions, and don’t be afraid to reengineer. That is how you scale.

They picked the wrong product in first place. MongoDB and Couchbase are two different databases.