This article on Oct 25th mentions Hibari in the “Erlang” section. As a Basho guy nowadays, I’m very slightly sad that the author didn’t also mention Riak, but as a Hibari fan, I’m quite happy.
Seven Programming Languages on the Rise: From Ruby to Erlang, once niche programming language are gaining converts in today’s enterprise. http://infoworld.com/d/developer-world/7-programming-languages-the-rise-620
Scott,
I’ve become quite interested in Hibari — the focus on immediate vs eventual consistency makes it quite different from many of the more well-known DHTs (Riak, cassandra, S3, dynamo, etc).
What problems do you see immediate consistency being advantageous vs eventual consistency? I know gemini did webmail and mobile messaging solutions (I’m quite familiar with those). As counter-point, Coda Hale makes a compelling argument about large scale systems most commonly suiting an eventually consistent model that I’m trying to reconcile vs the needs of our projects…
http://codahale.com/you-cant-sacrifice-partition-tolerance/
“…Given this economic context, it becomes clear why most practitioners at any interesting scale meet their business needs using highly-available, eventually consistent systems.”
best regards
–D
Don, it depends on the need for your app. For Gemini’s Webmail app, we likely would not have been able to meet the development deadline if we had to manage the extra complexity of a non-strictly-consistent system. The customer’s availability requirements were compatible with a strictly-consistent system, so … Hibari was a good choice.
-Scott