News for hackers. Stuff that matters.

A comment on MongoDB queries don’t always return all matching documents. Parent comment

Re:MongoDB queries don’t always return all matching documents by m_mueller on Tuesday June 07, 2016 @07:47PM (#11858977)
So my question is then: Why not use CouchDB instead? I don't see what Mongo gives you over that and CouchDB is at least dependable and predictable in its operation.
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by rdtsc on Tuesday June 07, 2016 @08:16PM (#11859119)
CouchDB is too reliable and actually fsyncs your documents to disk. That is plain boring. I like to live on the edge and have some documents go to /dev/null once in a while. Life is just more exciting that way ;-)

/s

[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by SmirkingRevenge on Wednesday June 08, 2016 @01:30AM (#11860231)
I really like Couch, I wish it had more adoption than it seems to have and that its ecosystem was more mature than it seems to be... and that javascript wasn't its first class citizen.

But its a really cool database (though I'm partial to rethinkdb now)

[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by derefr on Wednesday June 08, 2016 @03:16AM (#11860575)
Even Javascript is sort of a second-class citizen in Couch. The real first-class citizen is native Erlang code running unsandboxed in the server context. If you want high(er) performance, that's where you go. (Alternatives to this have been discussed, like embedding the luerl Lua interpreter to give the option of a sandboxed programming target without the IPC cost. Nothing in the immediate pipeline, though.)
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by dkersten on Thursday June 09, 2016 @07:36AM (#11868704)
though I'm partial to rethinkdb now

Me too. RethinkDB is my document database of choice these days. In my experience, its proven to be reliable and fast and the development team very responsive and helpful. They also seem quite mindful when it comes to new features and will delay things for years (eg auto-failover, which they now support but it took a while) if rushing it would impact quality.

That's what I want from a database: first and foremost it must be solid and not lose my data. Everything else (including high availability) can come after.

[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by s_kilk on Wednesday June 08, 2016 @03:55AM (#11860709)
Is CouchDB still alive? I spent a weekend playing with it in January, but it seemed to be a very quiet project, with the last stable release being almost two years ago.
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by m_mueller on Wednesday June 08, 2016 @09:02AM (#11861938)
Most of the activity happens at Couchbase now, the company that the inventor D. Katz founded based on CouchDB technology. You can still use Couchbase for free, but it's possible to pay for support. The coolest thing they have is Couchbase Lite, the mobile version of CouchDB, lets you replicate with your server. I find it a very interesting alternative to Core Data, parse and co. and we use it in production.
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by s_kilk on Wednesday June 08, 2016 @09:32AM (#11862140)
Good to know, will shift attention to Couchbase and re-assess. Thanks!
[ Parent | on HN ]