We talk often about various types of NoSQL databases – document stores like Apache CouchDB, graph databases like Neo4j and BigTable clones like Hbase. But we also occasionally talk about various attempts to improve the tried and true relational database model – projects like Drizzle (coverage), HandlerSocket (coverage), RethinkDB (coverage), TokuTek (coverage) and VoltDB (coverage).
The 451 Group dubs these “NewSQL” databases. In a blog post, 451 analyst Matthew Aslett explores this burgeoning category of database and adds several to our growing list of projects.
On the definition of NewSQL, Aslett writes:
“NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. We have previously referred to these products as ‘ScalableSQL’ to differentiate them from the incumbent relational database products. Since this implies horizontal scalability, which is not necessarily a feature of all the products, we adopted the term ‘NewSQL’ in the new report.
And to clarify, like NoSQL, NewSQL is not to be taken too literally: the new thing about the NewSQL vendors is the vendor, not the SQL.
In addition to the ones mentioned above, Aslett cites the following as NewSQL vendors:
- Clustrix
- GenieDB
- ScalArc
- Schooner
- ScaleDB
- Akiban
- CodeFutures
- ScaleBase
- Translattice
- NimbusDB
- MySQL Cluster with NDB
- JustOne DB
What do you think? Is this a helpful new term, or just more buzz wordism?
