Yesterday The 451 Group published a report asking “How will the database incumbents respond to NoSQL and NewSQL?”
That prompted the pertinent question, “What do you mean by ‘NewSQL’?”
Since we are about to publish a report describing our view of the emerging database landscape, including NoSQL, NewSQL and beyond (now available), it probably is a good time to define what we mean by NewSQL (I haven’t mentioned the various NoSQL projects in this post, but they are covered extensively in the report. More on them another day).
“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.
So who would be consider to be the NewSQL vendors? Like NoSQL, NewSQL is used to describe a loosely-affiliated group of companies (ScaleBase has done a good job of identifying, some of the several NewSQL sub-types) but what they have in common is the development of new relational database products and services designed to bring the benefits of the relational model to distributed architectures, or to improve the performance of relational databases to the extent that horizontal scalability is no longer a necessity.
In the first group we 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.
(Links provide access to 451 Group coverage for clients. Non-clients can also apply for trial access).
Clearly there is the potential for overlap with NoSQL. It remains to be seen whether RethinkDB will be delivered as a NoSQL key value store for memcached or a “NewSQL” storage engine for MySQL, for example. While at least one of the vendors listed above is planning to enable the use of its database as a schema-less store, we also expect to see support for SQL queries added to some NoSQL databases. We are also sure that Citrusleaf won’t be the last NoSQL vendor to claim support for ACID transactions.
NewSQL is not about attempting to re-define the database market using our own term, but it is useful to broadly categorize the various emerging database products at this particular point in time.
Another clarification: ReadWriteWeb has picked up on this post and reported on the “NewSQL Movement”. I don’t think there is a movement in that sense that we saw the various NoSQL projects/vendors come together under the NoSQL umbrella with a common purpose. Perhaps the NewSQL players will do so (VoltDB and NimbusDB have reacted positively to the term, and Tokutek has become the first that I am aware of to explicitly describe its technology as NewSQL). As Derek Stainer notes, however: ” In the end it’s just a name, a way to categorize a group of similar solutions.”
In the meantime, we have already noted the beginning for the end of NoSQL, and the lines are blurring to the point where we expect the terms NoSQL and NewSQL will become irrelevant as the focus turns to specific use cases.
The identification of specific adoption drivers and use cases is the focus of our forthcoming long-form report on NoSQL, NewSQL and beyond, from which the 451 Group reported cited above is excerpted.
The report contains an overview of the roots of NoSQL and profiles of the major NoSQL projects and vendors, as well as analysis of the drivers behind the development and adoption of NoSQL and NewSQL databases, the evolving role of data grid technologies, and associated use cases.
It will be available very soon from the Information Management and CAOS practices and we will also publish more details of the key drivers as we see them and our view of the current database landscape here.
Subscribe via RSS
48 comments ↓
[…] 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 […]
[…] 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 […]
[…] 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 […]
[…] 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 […]
[…] 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 […]
[…] 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 […]
[…] Group dubs these “NewSQL” databases. In a blog post, 451 analyst Matthew Aslett explores this burgeoning category of database and adds several to our […]
[…] the growing set of options in the information management space. In the process they also clarified what they meant by “NewSQL”. “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. […]
[…] hace algunas semanas que se está empezando a hablar del NewSQL, el mes pasado Matt Aslett desde el blog del grupo 451 daba su definición, con la intención de aclarar el concepto, de esta nueva rama del SQL. […]
[…] Aslett, a senior analyst at the 451 Group research firm, just over a month ago single-handedly launched a new database category by coining a great name for it,NewSQL. This is a nice play on the NoSQL […]
[…] Aslett, a senior analyst at the 451 Group research firm, just over a month ago single-handedly launched a new database category by coining a great name for it,NewSQL. This is a nice play on the NoSQL […]
[…] demeanour during NewSQL databases Analyst organisation The 451 Group recently coined the tenure NewSQL and described it as “shorthand for a several new scalable/high performance SQL database […]
[…] Group dubs these "NewSQL" databases. In a blog post, 451 analyst Matthew Aslett explores this burgeoning category of database and adds several to our […]
[…] Ni tout à fait SQL, ni tout a fait NoSQL, cette solution appartient à une nouvelle famille appelée ‘NewSQL‘. […]
[…] for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] — has an answer for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] — has an answer for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] — has an answer for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] — has an answer for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] — has an answer for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] — has an answer for the shortcoming of both “old SQL” and NoSQL. It’s called NewSQL (a term coined by 451 Group analyst Matthew Aslett) or scalable SQL, as I’ve referred to it in the past. Pushed by companies such as Xeround, […]
[…] Aslett from the 451 group created a term called “NewSQL”. On the definition of NewSQL, Aslett writes: “NewSQL” is our shorthand for the various new […]
[…] 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 […]
[…] disturbance in the force is over OldSQL vs NoSQL vs NewSQL. Warning, these are not crisp categories, there’s leakage all over the place, watch your […]
[…] disturbance in the force is over OldSQL vs NoSQL vs NewSQL. Warning, these are not crisp categories, there’s leakage all over the place, watch your […]
[…] disturbance in the force is over OldSQL vs NoSQL vs NewSQL. Warning, these are not crisp categories, there’s leakage all over the place, watch your […]
[…] part of a wave of products that are classified as “NewSQL”, or even ScalableSQL, solutions. These databases embrace the power of SQL and even relational databases, but build scalability and […]
[…] disturbance in the force is over OldSQL vs NoSQL vs NewSQL. Warning, these are not crisp categories, there’s leakage all over the place, watch your […]
[…] Aslett, a senior analyst at the 451 Group research firm, just over a month ago single-handedly launched a new database category by coining a great name for it,NewSQL. This is a nice play on the NoSQL […]
[…] is a term coined by 451 Group analyst Matthew Aslett to describe a a new wave of software projects that try to make RDBMSes more […]
[…] came into my radar was due to their open source roots. In the age of jargons, VoltDB falls under NewSQL category of databases. In this age go high volume data, a database like VoltDB is absolutely […]
Is NewSQL systems work as advertised then why should anyone use a NoSQL DB?…
Definitions While your statement about the state of things isn’t completely wrong, I don’t think it really captures the primary MySQL/NoSQL distinction. Your description takes more of a pro-NoSQL focus than I think reality warrants. I would put it th…
[…] == "undefined"){ addthis_share = [];}There is a lot of buzz about Hadoop, NoSQL, NewSQL and columnar MPP databases. But where is the actual value for businesses? Businesses need to have […]
[…] is a lot of buzz about Hadoop, NoSQL, NewSQL and columnar MPP databases. But where is the actual value for businesses? Businesses need to have […]
[…] // Comment | Print | RSS Login to Rate There is a lot of buzz about Hadoop, NoSQL, NewSQL, and columnar MPP databases. But where is the actual value for businesses? Businesses need to have […]
[…] technologies we have also seen the growth of alternate DBMS technologies like NoSQL and NewSQL that further help to analyze large chunks of data in non-traditional structures (for example using […]
[…] technologies we have also seen the growth of alternate DBMS technologies like NoSQL and NewSQL that further help to analyze large chunks of data in non-traditional structures (for example using […]
[…] any time soon. The 451 Group’s Matt Aslett doesn’t think so, either, and has christened NewSQL as a nice compromise position between the old world and the new. As Aslett posits, NewSQL is […]
[…] users to scale their databases without having to resort to complex manual sharding,” said Matt Aslett, research manager, data management and analytics at 451 Research, in a release. […]
[…] enable users to scale their databases without having to resort to complex manual sharding,” said Matt Aslett, research manager, data management and analytics at 451 Research, in a release. “Clustrix’s […]
[…] enable users to scale their databases without having to resort to complex manual sharding,” said Matt Aslett, research manager, data management and analytics at 451 Research, in a release. “Clustrix’s […]
[…] users to scale their databases without having to resort to complex manual sharding,” said Matt Aslett, research manager, data management and analytics at 451 Research, in a release. […]
[…] users to scale their databases without having to resort to complex manual sharding,” said Matt Aslett, research manager, data management and analytics at 451 Research, in a release. […]
[…] enable users to scale their databases without having to resort to complex manual sharding,” said Matt Aslett, research manager, data management and analytics at 451 Research, in a release. “Clustrix’s […]
[…] are a big deal when deciding whether to go with a NoSQL, NewSQL, an MPP RDBMS, or traditional […]
[…] http://blogs.the451group.com/information_management/2011/04/06/what-we-talk-about-when-we-talk-about… […]
[…] of new database development that refines the classic Relational database models. Think NoSQL and NewSQL. Here is a paper by Daniel Abadi who is responsible for some of the better NoSQL implementations […]
I am happy to see the hype dissipate between noSQL and newSQL. Most people just want more performance for their use case. So as long as we keep seeing websites powered by both I think that is being achieved.