NoSQL vs. NewSQL vs. distributed SQL: DZone's 2020 Trend Report

NoSQL vs. NewSQL vs. distributed SQL: DZone's 2020 Trend Report

Databases are evolving. For the past decade, we’ve read thinkpiece after thinkpiece taking firm stances on the “SQL vs. NoSQL” debate--some of which declaratively pronounce the death of SQL or the death of NoSQL. In DZone’s annual report on SQL v NoSQL database usage, we’re excited to see that we’re moving beyond that paradigm. What we’re seeing in this report is more nuanced, and a lot more exciting: the death of the “SQL vs. NoSQL” binary altogether. 

This is happening for a couple reasons. For one, more and more companies are using a combination of both for their business needs. They do not have one monolithic database--they run specific applications on the tools that best suit that workload. 58% of the companies surveyed in the report are using a combination of both. 


DZone's report finds that the use of SQL and NoSQL are neck and neck in the world of big data. But it is no longer strictly a winner-take-all competition. Instead, the research indicated that we’re moving toward a world in which the hybrid use of both database types is becoming the norm: nearly 60% of respondents said their organizations use both SQL and NoSQL to support big data efforts.

In the report, interviewees at Oracle, Cockroach Labs, and more back up this research with what they’re seeing on the ground with customers. 

Another key insight: many organizations rate their own usage of NoSQL as “Bad” or “Very Bad,” especially ones who started using NoSQL when it first came to market. It’s indicative of what CIOs state in the report's interviews: companies need to align on a core set of use cases and business goals in deciding their tooling, rather than just pick the trendiest new technology. 

A New Paradigm: Distributed SQL 

But there’s another reason for this massive shift. Whereas companies used to need to make important--and difficult--tradeoffs in choosing between a SQL or NoSQL database, there are new products in the distributed SQL category that don’t require these tradeoffs. Distributed SQL databases, like CockroachDB, are delivering the benefits of both SQL and NoSQL. They deliver the ease of use of SQL--no more “Very Bad” ratings coming in--alongside the scalability and resilience capabilities that come hand in hand with NoSQL.

An important caveat to note, when you’re shopping for a distributed SQL database: not all technologies labeling themselves as such actually meet the definition of a distributed SQL database.  

About the DZone Evolution of the Database Report 

DZone’s annual report is an attempt to answer the age-old “SQL or NoSQL” question. To do so, they compile original research from the DZone team as well as thought leadership from executives at Oracle, Cockroach Labs, and more. 

[Read the Report

Keep Reading

Join ordering, part II: The 'SQL'

Even in the 80’s, before Facebook knew everything there was to know about us, we as an industry had …

Read more
Query plan caching in CockroachDB

Since the 2.1 release, CockroachDB has had a cost-based optimizer. Rewriting a big component of an existing …

Read more
[podcast] Unscripted founders Q&A on CockroachDB 1.0

LISTEN ON: | SoundCloud |

Join the Cockroach Labs founders for an unscripted conversation about the dirty …

Read more