News for hackers. Stuff that matters.
Re:RethinkDB 1.16: cluster management API, realtime push by joseraul on Friday January 30, 2015 @03:34PM (#8974322)
From the FAQ: "For multiple document transactions, RethinkDB favors data consistency over high write availability. While RethinkDB is always CID, it is not always A."

What is the relation between write availability and A(tomicity)?

Re:RethinkDB 1.16: cluster management API, realtime push by coffeemug on Friday January 30, 2015 @04:06PM (#8974489)
slava @ rethink here.

I think this sentence is just phrased poorly. It means to convey that there is no atomicity across multiple documents, which is unrelated to the previous sentence. I've opened an issue to fix that: https://github.com/rethinkdb/docs/issues/633. Thanks for noticing!

Re:RethinkDB 1.16: cluster management API, realtime push by ptnapoleon on Friday January 30, 2015 @03:37PM (#8974341)
That seems like a confusion between the A in CAP and the A in ACID.