> Is anyone doing Change Capture (like the Databus project from LinkedIn) > directly out of Riak? Right now I have something hacked up using > Ripple+ActiveModel::Dirty, but I'd like to divorce it from our app > completely if possible. Was thinking a post-commit hook might work? End > goal is to feed it to a logging backend (in the Kafka sense of the word) > for other systems to feed off of. > > I'd love any pointers you might have to past posts I've missed (tried > searching the archive but came up dry), code, ideas, "tried it and it was a > pain", "that's a stupid idea", etc.
I was thinking about a similar idea, but I haven't followed it through yet. It is certainly harder than it looks, especially on the question of how to handle backpressure or what kind of guarantees are you able to satisfy. A queue semantics might work for my use case, where the event broker app receives events, stores them in Riak and passes them on to other clients or brokers. This could work if none of them is interested in event ordering or past events (e.g. if events are immutable change events, there is a client-side conflict resolution, and there is a separate place to store the latest known/accepted state for each object). It would be interesting to hear what others have achieved. Istvan _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
