SPRAIN is an acronym that refers to the six key factors driving the adoption of alternative data management technologies to traditional relational databases that are being ‘sprained’ as a result of being stretched beyond their normal capacity by the needs of high-volume, highly distributed or highly complex applications.

Those six key drivers, and their associated sub-drivers, are as follows:

Scalability – hardware economics
Performance – MySQL limitations
Relaxed consistency – CAP theorem
Agility – polyglot persistence
Intricacy – big data, total data
Necessity – open source

A selection of some of the key findings by nextbigfuture on high scalable databases includes

  1. The database market remains dominated by relational databases and the incumbent industry giants, but the emergence of NoSQL and NewSQL alternatives has in part been driven by the inability of these products to address emerging distributed and schema-less data management requirements.
  2. The NoSQL projects were developed in response to the failure of existing suppliers to address the performance, scalability and flexibility requirements of large-scale data processing, particularly for Web and cloud computing applications.
  3. NewSQL and data-grid products have emerged to meet similar requirements among enterprises, a sector that is now also being targeted by NoSQL vendors.

William Shulman, co-founder of MongoLab, a company that provides a Cloud-based hosted MongoDB solution. He explained:

I think the six key drivers [cited to be behind the adoption of alternative information management solutions Scalability, Performance, Relaxed Consistency, Agility, Intricacy and Necessity] miss something subtle and important, that to me is the reason why MongoDB is the next MySQL. It’s a data structure thing. MongoDB may have originally gotten attention because of the “mongo” (i.e. it can scale). But, I think the reason it is beloved by so many, for datasets both big and small, is the fact that it is a JSON object store. Having the ability to store complex data structures that mirror the objects in your code is what everyone has been waiting for for 15 years. Good bye object-relational mapping.

New information management solutions are rapidly being adopted even by large corporations because everybody is looking to cut cost and manage data effectively.

NewSQL Databases would include (in no particular order) Clustrix, GenieDB, ScalArc, Schooner, VoltDB, RethinkDB, ScaleDB, Akiban, CodeFutures, ScaleBase, Translattice, and NimbusDB, as well as Drizzle, MySQL Cluster with NDB, and MySQL with HandlerSocket. The latter group includes Tokutek and JustOne DB. The associated “NewSQL-as-a-service” category includes Amazon Relational Database Service, Microsoft SQL Azure, Xeround, Database.com and FathomDB.

Is NewSQL the future of Database Systems?