It is now official. Gigaom has confirmed: eventual consistency is dying: http://gigaom.com/2013/11/02/next-gen-nosql-the-demise-of-eventual-consistency/ …
@eachus it does, however Riak 2.0 added transactions and strong consistency too. k/v is still limiting though
-
-
@bascule I understand. My point was that there is evidence that you don't actually need to sacrifice consistency to availability. -
@eachus no there isn't. It's formally proven you have to -
@bascule I understand the CAP theorem. -
@eachus evidently you don't. Read Brewer's paper -
@bascule Apparently you aren't interested in what they had to say. Never mind. -
@eachus lots of crackpots in this space (much like crypto) -
@bascule You don't think it's possible tCAP is based on flawed assumptions? http://voltdb.com/clarifications-cap-theorem-and-data-related-errors/ … (That's not the paper I referred to.) -
@eachus I'll believe it when... https://issues.voltdb.com/plugins/servlet/mobile#issue/ENG-5342 … - 1 more reply
New conversation -
-
-
@bascule Not "proven", but the argument is interesting. I'll link the paper if I find it.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.