You may also want to have a look at this post by Aphyr. There are a LOT of caveats when trying to do this sort of thing.
http://aphyr.com/posts/254-burn-the-library -Andrew On Fri, Mar 22, 2013 at 9:02 PM, Sean Cribbs <s...@basho.com> wrote: > Datomic does something similar -- except that instead of updating keys > in-place, it only adds new values to Riak and advances the pointer(s) > to the current state in ZK. > http://www.infoq.com/presentations/Deconstructing-Database > > On Fri, Mar 22, 2013 at 7:32 PM, Andrew Berman <rexx...@gmail.com> wrote: > > Hello, > > > > I'm wondering if anyone has explored the idea of using Zookeeper in > front of > > Riak to handle locking. My thought is that a client goes to Zookeeper > to > > get a lock on a key before updating. Any other client that wishes to > update > > the same key must check for the existence of a lock. If it exists, an > error > > is thrown, if not, then it proceeds. Once the client is finished with > the > > key, it releases the lock. > > > > --Andrew > > > > _______________________________________________ > > riak-users mailing list > > riak-users@lists.basho.com > > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > > > > -- > Sean Cribbs <s...@basho.com> > Software Engineer > Basho Technologies, Inc. > http://basho.com/ > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
