News for hackers. Stuff that matters.
Re:Call me maybe: Elasticsearch by kansface on Thursday June 19, 2014 @02:58PM (#7917710)
Before you do that, check out http://aphyr.com/posts/285-call-me-maybe-riak
Re:Call me maybe: Elasticsearch by aaronblohowiak on Thursday June 19, 2014 @05:14PM (#7918350)
TL;DR: Aphyr talks at length about how riak is not a CP system, even though nobody claims that it is. Riak is AP. Aphyr demonstrates how this plays out in practice and gives an intro into CRDTs, which let you achieve something that is eventually correct for certain kinds of state transformations.
Re:Call me maybe: Elasticsearch by nosequel on Thursday June 19, 2014 @05:43PM (#7918467)
Every conclusion he comes to are also described on Basho's site when it comes to using last-write-wins. At the end of the post, notice CRDT's preserve 100% of writes, and the same could be had if allowing siblings. Punting on high-availability is different than the company being upfront about the tradeoffs.
Re:Call me maybe: Elasticsearch by rdtsc on Thursday June 19, 2014 @07:07PM (#7918770)
What do you mean? Are you saying it because Riak with sibling preservation is actually one of the few (if not the only) database that didn't drop writes.
Re:Call me maybe: Elasticsearch by rspeer on Saturday June 21, 2014 @12:46AM (#7924223)
So, what do you do with siblings in a searchable text index (the case that ElasticSearch is designed for)?