🧱NewSQL Database

NEW

Also known as: Distributed SQL Database

A relational database that provides ACID guarantees with horizontal scalability and high throughput similar to NoSQL systems.

DESCRIPTION

NewSQL databases retain SQL and relational integrity while scaling out across nodes. They deliver ACID transactions with distributed consensus, partitioning, and replication. Systems like Spanner, CockroachDB, TiDB, and VoltDB target OLTP workloads at global scale. Techniques include MVCC, 2PC/Percolator-style commits, TrueTime or hybrid logical clocks, and Raft/Paxos. NewSQL addresses the scalability gaps of traditional RDBMS without abandoning SQL. Trade-offs include operational complexity and consistency-latency costs. Use cases include high-throughput microservices, financial systems, and multi-region apps.

ALTERNATIVE DEFINITIONS

Wikipedia

NewSQL is a class of relational database management systems that seek to provide the scalability of NoSQL systems for online transaction processing workloads while maintaining ACID guarantees.

Defines NewSQL by combining OLTP scalability with ACID in RDBMS.

Source

Cockroach Labs

NewSQL refers to databases that offer the familiarity of SQL with the elastic scalability of NoSQL while preserving strong consistency and transactions.

Emphasizes SQL familiarity and strong consistency.

Source

VoltDB

NewSQL databases are designed to deliver ACID transactions and SQL with the scalability and performance needed for modern, high-throughput applications.

Focuses on high-throughput transactional performance.

Source

RELATED TERMS

Google Cloud Spanner CockroachDB VoltDB TiDB ACID Transactions Sharding Consensus Algorithm Horizontal Scalability

COMPETING TERMS

NoSQL Database Relational Database

RELATIONS

• Broader: Database

KNOWLEDGE AREAS

Data Storage & Operations Data Engineering Cloud

TARGET AUDIENCE

Data Architect Data Engineer Software Developer Cloud Architect Chief Technology Officer

EXTERNAL SOURCES

• Wikipedia - NewSQL
• Google Cloud Spanner - Globally distributed SQL database
• CockroachDB - Distributed SQL architecture
• TiDB - TiDB distributed SQL overview

TOP QUESTIONS

What problems does a NewSQL Database solve?

It scales OLTP horizontally while preserving ACID and SQL, addressing limits of traditional single-node RDBMS.

Category: Relevancy

How does a NewSQL Database compare to NoSQL?

NewSQL offers strong consistency and SQL transactions, while NoSQL often prioritizes availability, schema flexibility, and eventual consistency.

Category: Comparison

What are typical NewSQL Database use cases?

High-throughput financial systems, multi-region apps, user metadata, and operational microservices needing strict consistency.

Category: Example

What’s a risk of adopting a NewSQL Database?

Operational complexity and latency trade-offs from distributed consensus, especially across regions.

Category: Risks

How do NewSQL Databases maintain consistency?

They use consensus protocols like Raft or Paxos, multi-version concurrency control, and atomic commit protocols.

Category: Overview

Is SQL portability guaranteed across NewSQL Databases?

Mostly, but dialect differences and distributed features vary; test and adapt queries and drivers.

Category: Mistakes

How do NewSQL Databases handle schema changes?

Online schema changes with transactional DDL are common, but impact varies; plan migrations carefully.

Category: Management

What is the biggest misunderstanding about NewSQL Database?

That it’s a drop-in replacement for all workloads. Analytical workloads may still favor columnar warehouses.

Category: Misunderstanding

What metrics matter when evaluating a NewSQL Database?

P99 latency, cross-region consistency behavior, write throughput, failure recovery, and operational tooling quality.

Category: Requirements