2. MongoDB's design has historically been terrible; and, from my current experience with clients, is still a source of 'WTF's.
I just verified every single post of you on hackers news in last 12 months, and every one, in different DB discussions are doing the some shamefull plug about Realm.
E v e r y o n e.
And not a single disclaimer from you, not to mention some of your posts (like here, what janl pointed) are simply not true.
Disgracefull. I'm leaving this comment for anybody in the future doing check on you to notice this.
As silly as that sounds as a reason to choose CouchDB it demonstrates where the respective company's priorities lie.
CouchDB is a community-run Apache Software Foundation project (that has corporate contributors as well as individual contributors) at a much lower scale than MongoDB.
Of course MongoDB’s marketing is better, they are spending a lot of money on it. If you’d like to help out with CouchDB’s marketing, we can always use another helping hand :)
It's definitely impressive marketing but when I'm deciding on which tool to use that arguably works against them as opposed to for them.
"It's incredibly fast!" "It's web scale!" "It'll be able to drive itself cross country in a couple of months!"
And I think the unfounded/exaggerated hype bothered a lot of us, but like Tesla, the actual product seems to have improved quite a lot as they've had time and resources to throw at it. So sure, some of us remember Teslas and MongoDB from 2013 and scoff, but the current reality is much different.
> The Couch Replication Protocol lets your data flow seamlessly between server clusters to mobile phones and web browsers, enabling a compelling offline-first user-experience
CouchDB has another pattern, each master is really a master and you can have live replication but also offline replication. You can connect two clusters every new moon and they will synchronize. For sure the clients may have to deal with potential conflicts but in practice it's very neat and that's what makes couchdb worth it if you need this feature.
CA databases: SQL databases that are hard to scale ("partition") but are always consistent and available.
CP databases: MongoDB style databases that are consistent and partition tolerant, but trade availability (sometimes your queries will fail during high load).
AP databases: CouchDB style databases. They are always available and are partition tolerant, but you may be querying stale data.
They are very different databases. But since they have come up are around the same time and because they look very similar on the surface, you might think you chose between them.
But when you look more closely at detail decisions on the technical details, at almost every point, where CouchDB goes one way, Mongo went the other way.
I’m not saying either decisions are better or worse, it’s just that they are very different database that you should evaluate on their merits, not just superficially.
Seriously asking...
Over the past 5 years MongoDB has gotten a great storage engine, transactions, distributed transactions, multi master replication, first class change streams and is very very solid as a foundational piece of infrastructure you can rely on while CouchDB has languished. I can’t imagine reaching for it in my tool belt when I need a document store over MongoDB but I’m obviously biased so I’m wondering if there is a lot I’m missing.
Obviously it’s cool from a more open source databases standpoint — I love learning about how things are built and evolve over time.