11–20 of 31 posts
Biggest thing I can't stand about the new overhaul is the barrier for the open source version - I want to evaluate for my purposes, not give you my email. Been following Riak for some time now, and I'm hopeful this will do good things for Basho.
[0] https://github.com/basho/riak
(I work for basho)
Do I understand correctly that Basho is now a platform-as-service company, like Compose or Heroku, rather than an enterprise database product company?
Doesn't seem that way to me. I see it as a way of taking some elaborate service integration work and wrapping it up as a platform one might deploy in house.
Do I understand correctly that Basho is now a platform-as-service company, like Compose or Heroku, rather than an enterprise database product company?
(I work for basho)
Looks like a nice product, but I can't seem to find details on the internal message routing... Is it built on Redis pub/sub, Riak itself, or something else altogether? And I wish the branding was toned down. As it is, I'm reluctant to direct coworkers or friends to the site despite my interest.
[0] https://github.com/basho/riak_core [1] http://basho.com/understanding-riak_core-handoff/ [2] http://basho.com/understanding-riak_core-building-handoff/
(I work for basho)
Earlier quoted context omitted.
New CEO and CTO a year ago are a likely source of repositioning: http://basho.com/basho-names-new-ceo-and-cto/ I can't speculate on how that all relates to brain drain.
Given tweets like this one ( https://twitter.com/jtuple/status/598230043093897216 ), there doesn't seem to be much to speculate about.
But yeah, @jtuple, @Roach_B_me, and others have some choice tweets on the matter.
Off topic- your name is a fantastic book!
edit: (Although I think Orchestrate used HBase behind the scenes instead of Riak, which is probably a more appealing stack for Enterprises since Hadoop is more accepted than Riak.)
Earlier quoted context omitted.
New CEO and CTO a year ago are a likely source of repositioning: http://basho.com/basho-names-new-ceo-and-cto/ I can't speculate on how that all relates to brain drain.
Given tweets like this one ( https://twitter.com/jtuple/status/598230043093897216 ), there doesn't seem to be much to speculate about.
Earlier quoted context omitted.
Given tweets like this one ( https://twitter.com/jtuple/status/598230043093897216 ), there doesn't seem to be much to speculate about.
"Data gravity" ?
Basho has experienced some MAJOR brain drain in the last year. I wonder if this re-positioning is related to that.
The primary reason I left Basho is that I felt the company was turning into a "don't invent here" culture, the polar opposite of "not invented here". The goal was no longer to solve hard distributed systems problems and build amazing technology, but to just integrate various "trendy" technologies and make an enterprise simplification play.
The problem is that most of these other technologies have major failings and/or punt on the corner cases that us old time Basho engineers obsessed over.
The whole point of Riak was to be the most highly available, fault tolerant, trusted database you could use. You can't just integrate Riak with arbitrary products X, Y, and Z without compromising on those core tenants.
I really hope Basho can deliver on the promises they're making about this data platform product. I really do. But, for various reasons I can't really talk about, I'd say I'm extremely skeptical.
(BTW, for those that don't know me: I'm a former Principal Engineer at Basho and was the lead developer on a variety of sub-systems in Riak over the last four years)