Orchestrate was founded by ex-Basho people, built this product as a service, and have already been acquired. This is a pretty slow "fast follow."<p>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.)
Is anyone able to parse the explanation below for "Data Gravity"? Even with a great product like Riak, it's difficult to build a hypergrowth standalone business. So apparently they got Cloudera-envy, and decided to.. uh.. synergize new paradigms, and reintermediate plug-and-play partnerships, or something.<p>> Data gravity describes the effect that as data accumulates, there is a greater likelihood that additional services and applications will be attracted to this data, essentially having the same effect gravity has on objects around a planet. As the mass and density increases, so does the strength of the gravitational pull and as things get closer to the mass, they accelerate towards it at increasing velocity. Although services and applications have their own gravity, data is the most massive and dense, meaning it has the most gravity. If data becomes large enough it can become virtually impossible to move. Usually as services and applications interact with data, they cause even more rapid growth of the data itself, creating a continuous cycle of data growth.
I'm really excited by RiakCS (now rebranded as RiakS2) because when it works, it offers a powerful on-premise version of S3. I've been integrating it with Cloud Foundry for about a year now, repackaging it to deploy with BOSH, but it's been a constant source of frustration.<p>From an operator perspective it's incredibly hard to install and configure - the onboarding process to create a cluster from scratch is terrible and the outputted logs are often little more than erlang stack dumps. As an example, I've already spent days trying to get riak-cs 2.0 running on a stock ubuntu 14.04 machine. It should not be this difficult to stand up a product out of the box.<p>Basho's support engineers are generally well intentioned but often their response is "run the following erlang command, and reply to us with the response (also in erlang)". As an operator, I have no idea what effect the provided commands have on my system, now what the output should tell me. Similarly, it took months for their support/engineering team to answer a support ticket about garbage collection - eventually providing us some defaults such that RiakCS would perform garbage collection out of the box. They could not tell us why these settings would work, nor any side-effects of changing low-level parameters.<p>From a product perspective, Basho do not appear willing or able to support the open-source community around their products - typically every answer we've received boils down to "it depends on your use case" and effectively "it should work, I don't believe you are seeing the issues you are raising".<p>I really hope this 're-positioning' results in more support for operators and the community in general. RiakS2 has a lot of potential and I hope Basho are able to realize this.
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?<p>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.
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.<p>Been following Riak for some time now, and I'm hopeful this will do good things for Basho.