A dynamo-as-a-service offered by Amazon on their ecosystem will appeal to some. For others, the benefits of a Dynamo-inspired product that can be deployed on other public clouds, behind-the-firewall, or not on the cloud at all, will be critical.

Objective. Clear. To the point.

Original title and link: Basho: Congratulations, Amazon! (NoSQL database©myNoSQL)

via: http://basho.com/blog/technical/2012/01/18/Congratulations-Amazon/

Don Rippert interviewed by Derrick Harris (GigaOm):

Enterprises will start adopting NoSQL en masse, Rippert thinks, because the types of data they’re now dealing with require new technologies. “We are the data store for the new type of data being stored,” he explained. […]

That data is largely of the unstructured variety coming from web applications, machines and other sources that aren’t the traditional business-transaction data for which relational databases were created. Relational databases were the answer to almost everything previously, but now Rippert thinks NoSQL is “the answer to about 40 percent of business use cases today”.

A couple of follow up questions for Don Rippert^[1]:

1. Is your prediction of 40% market share relative to scenarios for large scale, unstructured data with high availability requirements? That would basically mean a 40% market share for just a couple of products: Cassandra, HBase, Riak, Project Voldemort, and (probably) Couchbase.

2. How is the rest of 60% of the market devided between the other NoSQL databases, NewSQL databases, and the traditional relational databases?

3. Considering the current market structure, when do you think the shift towards large scale, highly available requirements happened?

4. How long do you think it will take the market to remodel? What factors will accelerate this transition?

Original title and link: 40% Penetration for NoSQL: An Interview With Basho’s CEO Don Rippert (NoSQL database©myNoSQL)

via: http://gigaom.com/cloud/why-accentures-cto-made-the-move-to-nosql-startup-ceo/

After Innostore and Bitcask, Basho guys are currently experimenting with integrating Google’s LevelDB as a storage engine for Riak. Preliminary results are looking promising:

For most Riak users, Bitcask is the obvious right storage engine to use. It provides low latency, solid predictability, is robust in the face of crashes, and is friendly from a filesystem backup point of view. However, it has one notable limitation: total RAM use depends linearly (though via a small constant) on the total number of objects stored. For this reason, Riak users that need to store billions of entries per machine sometimes use Innostore (our wrapper around embedded InnoDB) as their storage engine instead. InnoDB is a robust and well-known storage engine, and uses a more traditional design than Bitcask which allows it to tolerate a higher maximum number of items stored on a given host.

It appears that LevelDB may become a preferred choice for Riak users whose data set has massive numbers of keys and therefore is a poor match with Bitcask’s model. Performance aside, it compares favorably to InnoDB on other issues such as permissive license and operational usability.

Original title and link: Riak Getting LevelDB as Storage Engine (NoSQL database©myNoSQL)

via: http://blog.basho.com/2011/07/01/Leveling-the-Field/

This couldn’t go unmentioned:

Basho Technologies, a data storage and management software startup serving the enterprise market, this morning announced that it has raised $7.5 million in Series D funding.

In addition, Basho announced that its board of directors has named Donald J. Rippert, long time CTO of Accenture, as the company’s new president and chief executive officer.

Couple of comments:

1. I couldn’t figure out if this is a completely new financing round than the $7.5mil. announced in February
2. The new CEO has been responsible for two main areas back at Accenture: the technology consulting organization and the research and development organization. That basically means a good perspective on the industry and lots of connections, but also knowledge of product development.

Original title and link: Basho: New Financing, New CEO (NoSQL database©myNoSQL)

via: http://www.techcrunchit.com/2011/06/29/big-data-storage-startup-basho-nabs-7-5m-and-accenture-cto-don-rippert/

Justin Sheehy (CTO Basho) answers Michael Coté’s (RedMonk) questions about Basho, the current state of NoSQL, and polyglot persistence adoptions among developers.

Original title and link: Basho, NoSQL, and Polyglot Persistence Adoption With Justin Sheehy (NoSQL database©myNoSQL)

via: http://www.redmonk.com/cote/2011/06/20/justin-sheehy-on-basho-nosql/

Kresten Krab Thorup continues his experiments becoming more and more of an advocate of Riak:

The module riak_link_index provides a mechanism that can be applicable for some situations, providing means to create synthetic (secondary link index) objects triggered by a Riak commit hook. The mechanism work by defining a function that names these synthetic objects as a function of the primary object body.

As far as I can tell Basho is already working on adding secondary indices to Riak.

Original title and link: Riak Secondary Indices using Links (NoSQL databases © myNoSQL)

via: http://www.javalimit.com/2011/04/using-to-index-riak-objects.html

After riak_core — the refactored Riak core that can be used for building distributed apps without shared state, Basho is releasing now riak_err:

The riak_err OTP application replaces about 90% of the default Erlang/OTP info/error/warning event handling mechanism. The replacement handler places strict limits on the maximum size of a formatted message. So, if you want to limit the maximum length of an error message to 64 kilobytes, you can. The result is that it’s now much more difficult to get Riak to crash due to error message handling.

riak_err is available on ☞ GitHub.

Gemini Mobile Technologies, the company behind Hibari, the distributed, high available key-value store, is open sourcing under Apache license cluster_info:

It provides a flexible and easily-extendible way to dump the state of a cluster of Erlang nodes. The app can also automatically gather all of this data from all nodes and write it into a single file. It’s about as easy as can be to take a snapshot of all nodes in a cluster.

Currently, cluster_info is packaged together with Hibari, but Basho will start distributing it with the next Riak release.

Original title and link: Basho and Gemini Mobile New Contributions to Erlang Cluster Management (NoSQL databases © myNoSQL)

via: http://blog.basho.com/2010/11/17/two-new-erlang/otp-applications-added-to-riak-products---'riak_err'-and-'cluster_info'/