rethinkdb

If you want to run a RethinkDB server on your mobile device that's a different scenario of course...

Since RethinkDB uses TCP connections, this shouldn't usually happen (since the TCP acknowledgements wouldn't get through either).

Many of our customers run RethinkDB in the cloud, and the latency between cloud regions can be quite punishing.

I was thinking about maybe toying with the idea of making a fully reactive RethinkDB package for Meteor.js.

I tried giving this a shot starting up 3 rethinkdb nodes with a proxy node with my existing application.

RethinkDB is fun, very technically challenging, well-funded, and is growing very quickly.

I think having servers with particularly unstable connectivity in a RethinkDB cluster is really uncommon though.

Finally, RethinkDB's needs are quite specialized and there isn't a service that does what we need out of the box.

RethinkDB does really well on the Jepsen tests in our internal testing.

What's the most mature client driver for RethinkDB, in your opinion?

RethinkDB is missing though, are you discontinuing that product?

We tried to use these libraries, but a project of RethinkDB's scope has a lot of abstractions for networking, threading, memory allocation, etc.

They provide a "When is RethinkDB not a good choice?" point, they provide a "stability report", and that report was a proper torture test, and they responded promptly to the issues raised by the Jepsen test.

This leads to far more solid and well tested operations practices that respect service interactions and you don't wind up with "we swept it under the rug" problems like the RethinkDB 2.1 beta announcement's "with only a few seconds of unavailability".