4 ms·

>it's an unlikely success story that deserves admiration Well, it's a success story due to marketing, smart marketing, clever marketing, and more marketing, no

>it's an unlikely success story that deserves admiration Well, it's a success story due to marketing, smart marketing, clever marketing, and more marketing, not due to lots of technical merits. And it was not the first document store to appear, just the most successful. For starters, CouchDB was previous to MongoDB.

thawkins 9y ago
Couch was a nightmare to use, mingo made all the friction to get it into products go away, especialy when teamed with dynamic languages.
- jared0x90 9y ago
  Did you really find CouchDB that bad to work with? I never in the end settled on either couch or mongo for a project long term but when I setup couch to test it out a few years ago I had it up and running with functional replication quite quickly (i.e., one afternoon) from being a complete novice with the platform. It's built in web panel at the time basically handled everything from basic setup to replication quickly.
- karmelapple 9y ago
  Using CouchDB on our team has been a pretty good experience; nothing like a nightmare. We used replication on the native apps for offline mode, kept things simpler with online-only for our web app, and have had a very good time overall. We are also using JSON schema for our CouchDB documents so we ensure we don't have all kinds of wild / wrong data showing up; if you had really hairy, unstructured data, I can see why a dynamic language might help with that bad situation, but for our use case, we were able to take advantage of the powerful replication built into CouchDB and get solid offline syncing for all of our native apps that also plays nicely with live updates in a web browser.
megaman22 9y ago
Notes was a document store before JSON, or even XML was even a thing. The wheel turns.
hinkley 9y ago
Reminds me of JBoss, right down to the astroturfing.
- munk-a 9y ago
  Honestly, this story being on the front page of hackernews might be another example of that astroturfing. It's not impossible that they're trying to drive that price up as much as possible before dumping their shares.

thawkins 9y ago

Couch was a nightmare to use, mingo made all the friction to get it into products go away, especialy when teamed with dynamic languages.

jared0x90 9y ago
Did you really find CouchDB that bad to work with? I never in the end settled on either couch or mongo for a project long term but when I setup couch to test it out a few years ago I had it up and running with functional replication quite quickly (i.e., one afternoon) from being a complete novice with the platform. It's built in web panel at the time basically handled everything from basic setup to replication quickly.
karmelapple 9y ago
Using CouchDB on our team has been a pretty good experience; nothing like a nightmare. We used replication on the native apps for offline mode, kept things simpler with online-only for our web app, and have had a very good time overall. We are also using JSON schema for our CouchDB documents so we ensure we don't have all kinds of wild / wrong data showing up; if you had really hairy, unstructured data, I can see why a dynamic language might help with that bad situation, but for our use case, we were able to take advantage of the powerful replication built into CouchDB and get solid offline syncing for all of our native apps that also plays nicely with live updates in a web browser.

megaman22 9y ago

Notes was a document store before JSON, or even XML was even a thing. The wheel turns.

hinkley 9y ago

Reminds me of JBoss, right down to the astroturfing.

munk-a 9y ago
Honestly, this story being on the front page of hackernews might be another example of that astroturfing. It's not impossible that they're trying to drive that price up as much as possible before dumping their shares.