Understanding the Evolution: SQL, NoSQL, and NewSQL Databases
This article outlines the three generations of databases—SQL, NoSQL, and NewSQL—explaining the limitations of traditional relational systems, the scalability and consistency trade‑offs of NoSQL, and how NewSQL combines distributed architecture with ACID guarantees, while also listing major NewSQL projects.
SQL's Issues
At the beginning of this century the Internet grew rapidly, increasing user scale and data volume while demanding 24/7 availability. Traditional relational databases became a bottleneck. Two common solutions are upgrading hardware, which eventually hits a performance ceiling, and sharding data across a distributed cluster of inexpensive machines.
Sharding improves scalability but introduces new challenges: data now spans multiple databases, requiring middleware to route queries. Simple operations work, but cross‑shard joins and transactions become painful, often forcing developers to handle complexity at the business layer.
Advantages and Limitations of NoSQL
NoSQL emerged by abandoning strong transactional guarantees and the relational model, focusing on high availability and scalability through automatic partitioning.
High availability and easy horizontal scaling.
Relaxed consistency leads to significant performance gains.
Schema‑free design offers great flexibility.
However, the lack of strong consistency can be problematic for enterprise applications that require strict guarantees, such as financial systems. Additionally, NoSQL databases do not support standard SQL, leading to compatibility issues and a fragmented API landscape.
NewSQL Features
NewSQL provides the same scalability as NoSQL while retaining the relational model and mature SQL query language, preserving ACID transaction properties.
In essence, NewSQL integrates NoSQL‑level scalability into traditional relational databases. Unlike classic SQL architectures, NewSQL is born for the cloud era and is inherently distributed.
Full SQL support for complex queries and big‑data analytics.
ACID transactions with configurable isolation levels.
Elastic scaling that is transparent to the application layer.
High availability with automatic disaster recovery.
Major NewSQL Projects
VoltDB
ClustrixDB
MemSQL
ScaleDB
TiDB
Reference: Pavlo et al., 2016 – NewSQL Survey
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.