MongoDB queries don’t always return all matching documents

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 ]