Fact-checked by Grok 2 weeks ago

NewSQL

NewSQL is a class of modern management systems (RDBMS) designed to deliver the scalability and performance of databases for (OLTP) workloads, while preserving the ACID (Atomicity, Consistency, Isolation, Durability) transaction guarantees and SQL interface of traditional s. These systems emerged as a response to the limitations of legacy RDBMS in handling massive-scale, distributed environments, such as those required by web-scale applications, without sacrificing relational or query expressiveness. The term "NewSQL" was coined in 2011 by analyst Matthew Aslett of 451 Research (now part of Market Intelligence) to describe a new generation of database technologies that bridge the gap between the rigid scalability constraints of monolithic SQL databases and the flexibility—but often weaker consistency—of alternatives. Early NewSQL systems, developed in the late and early 2010s, focused on innovations like shared-nothing distributed architectures, , and to achieve horizontal scaling across clusters. Key characteristics include support for standard SQL semantics, automatic sharding and replication for , and through mechanisms like multi-version concurrency control (MVCC), distinguishing them from 's eventual consistency models and traditional SQL's single-node bottlenecks. Notable examples of NewSQL databases include Google Spanner, which introduced globally distributed transactions with true-time semantics in 2012; , an in-memory OLTP system emphasizing low-latency processing; , a cloud-native solution inspired by Spanner for resilient, geo-distributed deployments; and MemSQL (now ), which combines row and column stores for hybrid workloads. Over the decade following its inception, the NewSQL landscape evolved amid challenges, with many initial vendors failing due to market adoption hurdles, leading to a shift toward "" paradigms by the early . Today, NewSQL influences cloud services like Amazon Aurora and drives trends in serverless, globally scalable databases, with the category's revenue reaching approximately $587 million in 2020 amid growing demand for relational scalability in enterprise and cloud environments. Recent advancements include the general availability of Amazon Aurora DSQL in May 2025, a serverless database offering virtually unlimited scale.

Definition and Goals

Core Principles

NewSQL represents a class of modern management systems (RDBMS) designed to provide ACID-compliant transactions and adherence to SQL standards while achieving horizontal scalability across distributed nodes. This approach addresses the limitations of traditional RDBMS, which often struggle with scaling beyond single-node deployments, by enabling systems to handle (OLTP) workloads with performance comparable to databases without compromising transactional integrity. The term was coined in 2011 by analyst Matthew Aslett to characterize emerging scalable SQL systems. A fundamental principle of NewSQL is the preservation of integrity, including structured schemas, support for complex joins, and enforcement of constraints, in contrast to the schema flexibility and often found in systems. These systems maintain the 's emphasis on normalized tables and , ensuring that data relationships remain enforceable even in distributed environments. This fidelity to relational principles allows developers to leverage familiar SQL querying without needing to adapt to non-relational paradigms, thereby reducing application complexity in scalable deployments. Central to NewSQL is the principle of non-blocking scalability, which permits linear performance improvements as additional nodes are incorporated into the , all while upholding guarantees. Unlike traditional RDBMS that may encounter bottlenecks from centralized locking or coordination, NewSQL s employ techniques such as multi-version (MVCC) or optimistic concurrency to minimize contention and enable seamless . This ensures that transaction throughput increases proportionally with hardware resources without degrading properties. NewSQL systems embody a nature by retaining the declarative of SQL and the foundational —encompassing operations like selection, projection, and join—while integrating paradigms such as shared-nothing partitioning. This combination allows for the distribution of data and computation across nodes, drawing from NoSQL-inspired methods to manage large-scale data volumes, yet it anchors operations in the rigorous mathematical framework of relational theory. Concepts from NewSQL have evolved into or overlapped with "" paradigms by the early 2020s, emphasizing cloud-native, geo-distributed relational databases. As a result, NewSQL facilitates both transactional processing and analytical workloads in a unified manner, often supporting (HTAP).

Motivations and Challenges Addressed

Traditional management systems (RDBMS) excel in providing ACID-compliant transactions and structured data handling but encounter substantial limitations in contemporary scenarios. These systems predominantly depend on vertical scaling—enhancing resources like CPU and memory on individual servers—which becomes inefficient and costly at massive scales, often failing to accommodate petabyte-level volumes without prohibitive hardware upgrades. Moreover, their single--centric designs introduce single points of failure, where crashes or can disrupt and halt operations across the entire . NoSQL databases arose to counter RDBMS scalability constraints by enabling horizontal scaling across commodity hardware clusters, yet they compromise on key reliability aspects. Most NoSQL implementations forgo full guarantees, relying instead on models that permit temporary data discrepancies during network partitions or high-concurrency writes, posing risks for applications requiring immediate accuracy. Additionally, by eschewing standard SQL in favor of diverse, vendor-specific APIs and query paradigms, NoSQL systems elevate the complexity of development and integration, thereby hindering developer productivity and portability across tools. NewSQL emerged to reconcile these divides, targeting the fusion of NoSQL's distributed with RDBMS's robust for handling petabyte-scale datasets in mission-critical domains. This approach ensures strong transactional support—encompassing atomicity, , , and —while facilitating horizontal expansion, making it ideal for high-stakes use cases like financial transactions where cannot be deferred. In 2025, NewSQL adoption is propelled by cloud-native imperatives and surging demands for real-time analytics alongside IoT-generated data streams, which necessitate resilient, scalable systems capable of processing vast, dynamic workloads without consistency trade-offs.

Historical Development

Origins in the Early

The term "NewSQL" was coined in 2011 by analyst Matthew Aslett of the 451 Research Group (formerly 451 Group) to describe a new generation of management systems (RDBMS) designed to address the limitations of traditional SQL databases while preserving (, , , ) properties. This terminology emerged in a 451 Research report that highlighted emerging vendors aiming to combine the familiarity of SQL with enhanced performance for large-scale workloads, distinguishing them from both legacy RDBMS and the rising alternatives. The conceptual foundations of NewSQL were heavily influenced by the movement, which gained prominence in the late 2000s as companies like and grappled with big data challenges that outstripped the capabilities of conventional relational databases. , introduced in 2006, and , detailed in 2007, exemplified NoSQL approaches that prioritized horizontal scalability and over strict , enabling massive distributed but often at the expense of full compliance. These innovations exposed the need for SQL-compatible systems that could similarly scale in distributed environments without sacrificing transactional integrity, prompting the NewSQL paradigm as a bridge between relational reliability and NoSQL elasticity. Early theoretical discussions around 2010–2012 focused on enabling distributed transactions, laying groundwork for NewSQL architectures through innovations in scheduling and replication. Seminal works included the Calvin system, proposed in 2012, which introduced deterministic transaction ordering to minimize coordination overhead in partitioned databases while ensuring . Similarly, Google's Spanner, outlined in the same year, demonstrated globally distributed transactions using TrueTime for external consistency, influencing subsequent designs for clock-synchronized guarantees across data centers. These papers addressed core challenges in maintaining and in shared-nothing environments, providing theoretical models that early NewSQL efforts would build upon. Initial motivations for NewSQL were intertwined with the rapid rise of in the late 2000s, which demanded databases capable of elastic for web-scale applications without the bottlenecks of single-node RDBMS. Early prototypes, such as (emerging from the H-Store research project around 2008–2010) and systems like Clustrix and Scalable SQL (later ScaleBase), focused on processing through in-memory storage and sharding to handle high-throughput OLTP workloads in settings. These efforts targeted the limitations of vertical scaling in clouds, offering horizontal while retaining SQL interfaces for developer productivity.

Evolution and Key Milestones

The evolution of NewSQL began to take shape in the early 2010s with foundational advancements that addressed the limitations of traditional relational databases in distributed environments. A pivotal milestone was the publication of the Google Spanner paper in 2012, which introduced a globally distributed database system providing strong consistency and ACID transactions across data centers using TrueTime for external consistency. This work laid the groundwork for scalable, relational systems capable of handling planetary-scale data. Complementing this, VoltDB advanced in-memory optimizations during this period, with a 2015 release enhancing real-time analytics on streaming data through its scale-out, ACID-compliant architecture designed for high-velocity OLTP workloads. From 2016 to 2020, NewSQL saw significant growth in open-source adoption, driven by the need for cloud-native solutions that combined SQL familiarity with scalability. CockroachDB's release of version 1.0 in May 2017 marked a key achievement, delivering production-ready with multi-active availability and automatic sharding for larger datasets. This period also featured increasing integration with for orchestration, exemplified by CockroachDB's support for deployments starting in late 2020, enabling resilient, containerized database operations in cloud environments. Overall, NewSQL revenues reached $587 million by 2020, reflecting broader market traction among providers. The years 2021 to 2025 witnessed NewSQL maturing into enterprise-grade technologies, with innovations tailored for and hybrid cloud demands. YugabyteDB's 2.17 release in December 2022 introduced advanced business continuity and disaster recovery features, such as multi-region replication, to support mission-critical applications. enhanced its platform in October 2023 with indexed vector search capabilities, enabling hybrid semantic and keyword queries for real-time workloads. Similarly, incorporated -driven query optimization in 2024, using to reduce query execution times by an average of 25% in complex HTAP scenarios. These developments expanded NewSQL's role in diverse ecosystems. The accelerated migrations by three to four years, boosting NewSQL's adoption in hybrid and multi- setups for their resilience and scalability in scenarios. This shift, partly driven by the demand for flexible infrastructures, positioned NewSQL systems as essential for distributed, fault-tolerant across on-premises and environments.

Technical Architectures

Distributed Shared-Nothing Designs

In distributed shared-nothing designs, a hallmark of NewSQL systems, data and processing resources are partitioned across multiple independent s, where each node exclusively owns its local storage and compute capabilities without sharing or disk with others. This architecture ensures that local operations, such as reads and writes on partitioned data, occur with minimal inter-node communication, as queries are routed directly to the relevant data locations. By avoiding centralized bottlenecks inherent in shared-memory or shared-disk models, shared-nothing enables NewSQL databases to handle high-throughput transactional workloads efficiently. The primary benefits of this design lie in its support for horizontal scaling and fault isolation. Adding allows for linear increases in throughput, as data can be repartitioned to distribute load evenly, achieving for (OLTP) applications that process millions of transactions per second across commodity hardware. Fault isolation is another key advantage: a on one node impacts only its local partition, preventing cascade effects across the , while replication mechanisms (handled separately) ensure data durability without compromising independence. This approach aligns with NewSQL's goal of scalable ACID compliance by optimizing for distributed execution from the ground up. Implementation typically involves data distribution strategies like hashing or range partitioning to assign records to nodes. In hashing, a applied to a partitioning (e.g., a ) deterministically maps tuples to specific nodes, ensuring even distribution and fast local lookups. Range partitioning, conversely, divides data based on ordered value of the , which facilitates easier rebalancing during node additions or failures but may lead to hotspots if data skews occur. These methods enable the creation of global tables in a distributed , where the entire appears unified to applications despite physical partitioning. A notable is the added complexity in handling operations that span multiple nodes, such as joins or aggregations across partitions, which require data shuffling and can introduce due to overhead. This necessitates optimized and query to minimize cross-node traffic, though it preserves the overall for partition-local workloads. While autonomic tools can mitigate challenges, the design demands careful initial partitioning to avoid imbalances that could undermine performance gains.

Consensus and Replication Mechanisms

NewSQL systems rely on distributed protocols to coordinate data replication across nodes, ensuring both durability and in the face of failures. These protocols, such as and , enable and log replication, where a leader node proposes updates that are acknowledged by a of replicas before commitment. For instance, Google's Spanner employs state machines on each spanserver to replicate data synchronously within and across datacenters, achieving linearizable consistency by agreeing on transaction logs. Similarly, implements for each key-value range, where the leader replicates writes to followers, and only a acknowledgment confirms the operation, preventing data loss even if minority nodes fail. This approach builds on shared-nothing partitioning by adding coordination layers for fault-tolerant agreement. Replication in NewSQL often adopts multi-master models through consensus-driven , balancing synchronous and asynchronous strategies to meet requirements. Synchronous replication, as in or , ensures that writes are durable across a before acknowledgment, providing for both reads and writes—meaning operations appear from any node's perspective. Asynchronous variants may follow for read replicas to reduce latency, but NewSQL prioritizes synchronous for guarantees, with systems like using to elect new leaders in seconds during failures, maintaining availability without data divergence. This contrasts with in by enforcing strict ordering via replicated logs, though it introduces coordination overhead that NewSQL mitigates through efficient sizing. To handle node outages, NewSQL employs quorum-based reads and writes, tolerating failures up to (n-1)/2 in an n-node replica group while preserving high availability targets like 99.999% uptime. Writes succeed if acknowledged by a write quorum (typically a majority), and reads query a read quorum intersecting prior write quorums to ensure freshness, as implemented in Spanner's Paxos groups where cross-zone replication sustains operations despite zonal failures. CockroachDB's Raft similarly uses majority quorums for log appends, enabling automatic failover and recovery without manual intervention. The evolution toward geo-replication in NewSQL addresses global distribution by extending across regions, incorporating optimizations in modern environments. Spanner's Paxos-based replication spans continents, using atomic clocks (TrueTime) to bound uncertainty and minimize commit delays, achieving sub-10ms for intra-region operations and handling cross-region syncs within hundreds of milliseconds. As of 2025, systems like support multi-region deployments with Raft-based protocols and declarative locality controls, routing writes to local leaders while using follower reads for low-latency access from local replicas, achieving in the tens of milliseconds for regional operations depending on region proximity and configuration in AWS or GCP setups.

Core Features

ACID Transactional Guarantees

NewSQL databases uphold the (, , , ) properties central to relational systems, adapting them to distributed architectures through specialized protocols that coordinate across nodes without compromising reliability. These guarantees distinguish NewSQL from alternatives, enabling scalable (OLTP) while preserving in the face of failures, concurrency, and geographic distribution. Some NewSQL systems, such as Google's Spanner, employ distributed two- commit (2PC) protocols to achieve atomicity, where a prepare collects votes from participating nodes before a commit finalizes changes. In Google's Spanner, 2PC is integrated with replication groups, coordinating commits across shards only if all groups agree, thus preventing partial updates. Lightweight alternatives, such as Spanner's TrueTime API—which leverages atomic clocks and GPS for bounded uncertainty in timestamps—enable efficient commit ordering without full 2PC overhead in low-latency scenarios. CockroachDB implements atomicity via a record serving as a "switch," changes as write intents during execution and atomically flipping to committed or aborted only after , ensuring no intermediate states persist. Consistency in NewSQL maintains , guaranteeing that concurrent distributed produce results equivalent to some serial execution order and preventing anomalies like lost updates or write skews. This is often realized through snapshot isolation combined with multi-version (MVCC), where each reads from a consistent snapshot of the database at its start timestamp. Spanner enforces external — a stronger form where order matches order—using TrueTime to assign monotonically increasing global timestamps during commits, even across centers. achieves serializable via MVCC and hybrid logical clocks, versioning to detect and resolve conflicts by aborting and retrying that violate . Isolation in NewSQL supports ANSI SQL levels such as repeatable read or serializable, shielding from interference while handling distributed contention. Mechanisms like MVCC allow non-blocking reads from historical versions, avoiding locks on reads, though writes may acquire short-term locks to manage intents. Distributed , arising from cross-node lock cycles, are mitigated through timeout-based detection and automatic retries; for example, CockroachDB's serializable (the default) restarts on conflict errors (code 40001), with built-in retry logic for small results up to 16 KiB to resolve contention without manual intervention. Repeatable read, when supported, ensures consistent views within a transaction but may still require deadlock avoidance via optimistic concurrency or ordering. Durability guarantees that once a transaction commits, its effects survive system failures, achieved by write-ahead logging (WAL) where changes are appended to a replicated log before acknowledgment. In distributed NewSQL, WAL entries are synchronously replicated across nodes using consensus protocols like or , ensuring majority acknowledgment prior to commit. Spanner, for instance, replicates WAL via state machines, providing durability even if individual nodes fail, with data persisted to stable storage post-replication. This replication ties into broader consensus mechanisms for , confirming logged changes across the cluster.

Scalability and Sharding Techniques

NewSQL systems achieve horizontal scalability primarily through sharding, which partitions data across multiple nodes to handle growing workloads efficiently. Automatic data partitioning occurs based on shard keys, typically using or methods to divide tables into smaller, manageable units called or tablets. This approach ensures even load distribution and supports parallel query execution, allowing the system to scale linearly with additional nodes. For instance, automatically shards tables into tablets using hash-based partitioning on the , distributing them across nodes for balanced storage and processing. Rebalancing is a critical component of sharding, enabling dynamic adjustments when nodes are added or removed from the cluster. During rebalancing, the system migrates between nodes to alleviate imbalances caused by data skew or workload shifts, often without interrupting ongoing operations. , for example, performs automatic rebalancing by redistributing ranges (its sharding units) across nodes upon cluster changes, ensuring optimal resource utilization and preventing performance bottlenecks. This process relies on background tasks that monitor shard sizes and access patterns to trigger migrations proactively. Elastic scaling extends these sharding capabilities in cloud-native environments, allowing clusters to expand or contract resources on demand. Auto-scaling mechanisms detect workload spikes and provision additional nodes, while live data migrations transfer shards seamlessly to new nodes with minimal downtime—often seconds or less. Systems like support this by dynamically adjusting compute and storage independently, integrating with cloud orchestrators such as for hands-off operation. While maintaining guarantees imposes some constraints on scaling speed, these techniques prioritize rapid adaptation to varying demands. Transparent sharding further enhances usability by abstracting the distribution logic from applications, routing queries automatically to the relevant without requiring client-side modifications. or embedded coordinators parse SQL statements, identify target via , and federate execution across nodes, presenting a unified database view. In NewSQL architectures, this is often implemented through centralized components that manage partitioning and query dispatch, as seen in early systems like those using ScaleArc . These techniques culminate in high-performance outcomes, with NewSQL databases leveraging in-memory storage and to reach millions of in benchmarks. For example, demonstrated 1.26 million inserts per second and 2.8 million selects per second on a 100-node using sharded, in-memory operations, highlighting the efficacy of horizontal distribution for workloads in 2019 benchmarks. Similarly, in-memory NewSQL implementations like have achieved over 1.2 million operations per second in YCSB-like benchmarks on modest hardware in earlier evaluations.

SQL Compatibility and Query Engines

NewSQL databases adhere to ANSI SQL standards, enabling seamless with existing relational applications while operating in distributed environments. This includes for complex operations such as multi-table joins, subqueries, aggregate functions, and window functions, executed across sharded data partitions without requiring application modifications. For instance, systems maintain relational integrity and SQL semantics, allowing developers to leverage familiar query patterns for (OLTP) workloads at scale. Distributed query engines in NewSQL architectures facilitate execution of SQL queries through cost-based optimizers that generate plans tailored for multi-node clusters. These engines push down computations to data-local nodes, minimizing and leveraging shared-nothing designs to achieve low-latency processing. Query routing often integrates with sharding mechanisms to direct operations to relevant partitions, ensuring efficient handling of distributed joins and aggregations via techniques like broadcast or repartitioning. Such optimizations enable horizontal scalability while preserving SQL expressiveness. To address limitations of traditional SQL in large-scale scenarios, NewSQL extends the language with features for specialized data types, including time-series functions (e.g., rolling aggregates over temporal data). As of 2025, many NewSQL systems also support geospatial queries through extensions like for spatial indexing and distance calculations. Hybrid query processing in contemporary NewSQL systems unifies OLTP and (OLAP) workloads, often through vectorized execution models that process data in columnar batches for improved CPU efficiency. This approach supports real-time analytics on transactional data and facilitates integrations with and pipelines, such as embedding vector similarity searches within standard SQL queries, as seen in systems like , , and as of 2025.

Notable Implementations

Commercial Systems

Google Cloud Spanner is a proprietary NewSQL database offering global distribution across multiple data centers, leveraging the TrueTime API to ensure external for transactions without sacrificing . This API provides bounded uncertainty in timestamp assignment, enabling at planetary scale, which is critical for mission-critical applications. Spanner powers high-stakes services such as , handling billions of reads and writes daily while maintaining low-latency access worldwide. Its adoption in enterprise environments underscores its role in supporting distributed shared-nothing architectures with automatic sharding and replication. SingleStore, formerly MemSQL, emphasizes an in-memory architecture combined with universal storage that unifies rowstore and columnstore formats for both transactional and analytical workloads. This design facilitates real-time on operational data, processing queries in milliseconds without ETL processes, and supports (HTAP). A key differentiator is its native support for vector embeddings, enabling and AI-driven applications like recommendation engines directly within the database. In September 2025, SingleStore underwent a growth buyout led by Vector Capital, reinforcing its position in enterprise . Enterprise adoption includes major firms such as for financial and for industrial AI integrations, highlighting its scalability in production environments. VoltDB, rebranded as , focuses on in-memory OLTP for high-velocity workloads, delivering sub-millisecond latency through deterministic and stored procedures. It optimizes for low-latency streaming ingestion, processing events in real-time with guarantees, which is essential for applications requiring immediate . Integrations for allow deployment in distributed environments, such as telecom networks, where it supports dynamic reactions to streams with minimal resource overhead. Notable enterprise users include for cloud mobility solutions and for real-time analytics in FusionInsight, demonstrating its efficacy in latency-sensitive sectors. NuoDB provides through its , distributed SQL engine, allowing seamless integration with multiple models while maintaining full compliance. Its domain-based sharding uses engines for query and managers for , enabling automatic based on domains without manual partitioning. This architecture emphasizes administrative simplicity in hybrid setups, supporting active-active replication across on-premises, , and public clouds for continuous availability. Adopted by organizations like for high-frequency OLTP in engineering simulations, NuoDB excels in environments demanding . Commercial NewSQL systems dominate in sectors due to their blend of SQL familiarity, reliability, and horizontal scalability, addressing regulatory needs for consistent at volume. As of , these offerings contribute significantly to the overall NewSQL market growth, with revenues projected to reach approximately $1.5 billion globally, driven by deployments in banking and trading platforms.

Open-Source Projects

Open-source NewSQL projects have significantly contributed to the ecosystem by providing modifiable codebases under permissive licenses, enabling community-driven innovation and reducing barriers to entry for scalable, ACID-compliant databases. These initiatives often leverage distributed architectures to combine SQL familiarity with horizontal scalability, fostering adoption in cloud-native environments. , initially released in 2015, is a prominent open-source database that implements PostgreSQL-wire , allowing seamless integration with existing tools and drivers. It employs the consensus algorithm for data replication and , ensuring across nodes by requiring a for writes. This design supports resilient multi-region deployments, with default replication across at least three nodes to enable always-on availability and global scalability. YugabyteDB is an open-source, cloud-native database that achieves compatibility through its YSQL API, which reuses the query layer for relational operations. Its storage layer draws inspiration from , providing wide-column capabilities for and geo-distribution via synchronous or asynchronous replication. The system supports multi-API access, including YSQL for SQL workloads and YCQL for NoSQL (Cassandra-compatible) queries, enabling flexible handling of diverse data models while maintaining guarantees. TiDB, developed by PingCAP since 2015, is an open-source distributed NewSQL database fully compatible with the 8.0 protocol, facilitating easy migration of MySQL applications without code changes. It supports hybrid transactional and analytical processing (HTAP), allowing real-time OLTP and OLAP workloads on the same dataset through its decoupled compute-storage architecture. Integrated within PingCAP's ecosystem, pairs with tools like TiKV for key-value storage and TiFlash for analytical acceleration, enhancing its utility in cloud-native setups. The Community Edition serves as the open-source variant of , offering full application compatibility for high-velocity, in-memory SQL processing under the AGPL license. Designed for low-latency OLTP workloads, it stores data primarily in to maximize throughput while supporting disk snapshots for durability. Extensions in the community edition cater to applications through real-time streaming and to via lightweight, embeddable deployments that align with event-driven architectures. Adoption of open-source NewSQL databases has grown among startups by 2025, driven by their cost-effectiveness in avoiding proprietary licensing fees and native integration with for orchestrated, scalable deployments. These projects enable and horizontal without vendor lock-in, with market analyses projecting continued expansion in and environments.

Use Cases and Applications

Industry-Specific Deployments

In , NewSQL databases enable fraud detection and high-throughput trading platforms by leveraging guarantees to ensure compliance with regulatory standards such as PCI DSS. For instance, serves as a distributed OLTP database that stores and indexes financial transactions, supporting vector-based models for and achieving latencies while scaling write throughput near-linearly across clusters. This allows processing of high transaction per second () volumes, such as those in stock exchanges, without compromising data consistency. Similarly, Volt Active Data facilitates intraday trading and fraud prevention by acting as both a and database of record, delivering predictable low under 20 milliseconds for decision-making on massive data streams. In , NewSQL systems support inventory management and recommendation engines that scale seamlessly to handle peak loads, such as during high-traffic events like , through transparent sharding and horizontal scalability. provides a single logical database for global order and inventory tracking, enabling a unified view of data across regions and optimizing revenue capture by automating stock synchronization in . , another NewSQL solution, has been adopted by logistics and firms like to scale out MySQL-compatible workloads on , managing inventory updates and order processing without downtime during traffic surges. These deployments maintain SQL compatibility for complex queries on customer behavior while ensuring transactions for reliable payment and stock adjustments. Healthcare applications utilize NewSQL for patient data systems that demand global availability and strict consistency to meet standards like HIPAA, facilitating secure storage and retrieval of (PHI). CockroachDB, being HIPAA-ready, supports resilient, cloud-native architectures for electronic health records (EHR) and platforms, with geo-partitioning to ensure low-latency access across multi-region deployments and 3x data replication for . This enables hospitals and providers to manage sensitive patient data without interruptions, supporting use cases like real-time treatment tracking while adhering to requirements for and audit logging. The distributed nature of NewSQL ensures that scalability features, such as automatic sharding, enhance during global patient queries. In telecommunications, NewSQL databases power 5G network analytics by processing massive event streams with low-latency queries, enabling operators to monitor traffic and optimize performance in real time. Volt Active Data excels in 5G environments by combining ACID compliance with sub-10-millisecond processing for billing, fraud detection, and personalized services, outperforming NoSQL in consistency for critical telco workloads. A major U.S. telecom provider migrated to CockroachDB from Amazon Aurora to deliver always-on customer experiences with resilient, distributed SQL queries. These implementations ensure fault-tolerant operations across edge nodes, vital for maintaining service quality amid surging data volumes.

Comparisons with NoSQL and Traditional RDBMS

NewSQL databases address limitations in traditional management systems (RDBMS) by enabling horizontal scalability across distributed nodes while preserving transactional guarantees, though this distributed design increases operational complexity compared to the simpler, vertically scalable architecture of traditional RDBMS like those optimized for single-node OLTP. Traditional RDBMS remain preferable for smaller-scale deployments where ease of management and low-latency single-server performance are prioritized over massive data distribution. Relative to NoSQL databases, NewSQL provides robust consistency models and SQL compatibility, facilitating easier integration with existing relational tools and applications that demand strong durability, but sacrifices some of NoSQL's schema flexibility for handling diverse, formats. NoSQL systems, by contrast, offer superior raw speed for write-intensive operations under , making them ideal for high-velocity data ingestion without the overhead of full transactional support. In performance benchmarks, NewSQL systems demonstrate substantial advantages in distributed transactional workloads, outperforming traditional RDBMS and in scenarios requiring , such as IoT sensor data processing. However, for non-transactional workloads emphasizing over strict , can deliver lower and higher peak throughput than NewSQL, which incurs additional overhead from distributed consensus mechanisms like two-phase commit. NewSQL is particularly suited for applications demanding both horizontal scalability and reliability, such as platforms handling global user transactions, whereas traditional RDBMS fit smaller, centralized OLTP needs and excels with unstructured, high-ingestion data volumes.

References

  1. [1]
    [PDF] What's Really New with NewSQL? - CMU Database Group
    In the last five years since we first coined the term NewSQL [18], ... The 451 Group, May 2012. [20] J. Baulier, P. Bohannon, S. Gogate, S. Joshi ...
  2. [2]
    Ten years of NewSQL: Back to the future of distributed relational ...
    Jun 3, 2021 · 451 Research first used the term NewSQL in 2011 to describe a selection of new relational database vendors. A decade on we examine the ...
  3. [3]
    What's Really New with NewSQL? | ACM SIGMOD Record
    The term NewSQL was first used by one of the authors of this article in a 2011 business analysis report discussing the rise of new database systems as ...Abstract · Cited By · Information & ContributorsMissing: origin | Show results with:origin
  4. [4]
    [PDF] NewSQL Principles, Systems and Current Trends - IEEE BigData
    NewSQL is the hottest trend in database management: • Scales out but without renouncing to SQL and. ACID transactions. • NewSQL has different roots leading ...
  5. [5]
    Relational vs. NoSQL data - .NET - Microsoft Learn
    NewSQL databases. NewSQL is an emerging database technology that combines the distributed scalability of NoSQL with the ACID guarantees of a relational database ...
  6. [6]
    NewSQL databases: The bridge between SQL and NoSQL
    Oct 12, 2020 · NewSQL databases attempt to provide enterprises with the top benefits of both relational and NoSQL databases on one platform.Missing: goals RDBMS petabyte-
  7. [7]
    What is NewSQL? - Aerospike
    Key features of NewSQL · SQL compatibility with scalability and performance · ACID compliance · Distributed, shared-nothing architecture · High availability and ...Missing: history | Show results with:history
  8. [8]
    NewSQL: Everything You Need to Know - DbVisualizer
    Rating 4.6 (146) · $0.00 to $229.00 · DeveloperNewSQL is a class of modern relational database management systems (RDBMS) that incorporate the best of both traditional SQL and NoSQL databases.Missing: definition | Show results with:definition
  9. [9]
    [PDF] How will the database incumbents respond to NoSQL and NewSQL?
    Apr 4, 2011 · How will the database incumbents respond to NoSQL and. NewSQL? 451 TECHDEALMAKER. 4 April 2011 – Sector IQ. Page 2. 451 TechDealmaker.Missing: origin | Show results with:origin
  10. [10]
    NoSQL, NewSQL and Beyond - InfoQ
    Apr 19, 2011 · “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. [...NewSQL vendors] have in common the ...Missing: origin | Show results with:origin
  11. [11]
    [PDF] Calvin: Fast Distributed Transactions for Partitioned Database Systems
    May 20, 2012 · Calvin is a transaction scheduling and data replication layer using deterministic ordering to reduce contention costs in distributed ...Missing: theoretical | Show results with:theoretical
  12. [12]
    https://www.infoq.com/news/2011/04/newsql/
  13. [13]
    [PDF] Spanner: Google's Globally-Distributed Database
    This paper describes how Spanner is structured, its feature set, the rationale underlying various design decisions, and a novel time API that exposes clock ...
  14. [14]
    VoltDB Targets Fast NewSQL Big Data Development - ESJ
    Jan 30, 2015 · NewSQL company VoltDB Inc. updated its namesake in-memory, scale-out database for faster real-time analyics on streaming data.Missing: milestones | Show results with:milestones
  15. [15]
    CockroachDB 1.0 is production-ready
    May 10, 2017 · CockroachDB earns its NewSQL stripes by providing distributed SQL to accommodate ever-larger data sizes and multi-active availability, a new ...Cockroachdb 1.0 · Distributed Sql · Multi-Active Availability
  16. [16]
    CockroachDB adds Kubernetes and geospatial data support - ZDNET
    Nov 10, 2020 · The new release is adding a key feature well-suited to a distributed transaction database and makes the platform cloud-native.
  17. [17]
    YugabyteDB 2.17 and New YugabyteDB Managed Features Focus ...
    Dec 8, 2022 · YugabyteDB 2.17 introduces key innovations to help power an enterprise's business continuity and disaster recovery (BCDR) strategy. This release ...
  18. [18]
    SingleStore Announces Several New Product Innovations to Unlock ...
    Oct 17, 2023 · New product innovations announced include: SingleStore Scope, a state-of-the-art hybrid search that combines fast vector search and fulltext ...
  19. [19]
    Transforming TiDB with AI: HTAP, Scalability & Real-World Cases
    Aug 12, 2024 · Query Optimization: AI algorithms optimized complex queries, reducing execution times by 25% on average. Workload Forecasting: Accurate workload ...
  20. [20]
    Pandemic lockdowns accelerated cloud migration by three to four ...
    Sep 2, 2021 · Pandemic lockdowns accelerated cloud migration by three to four years, with a spike in cloud-related questions on Stack Overflow.Missing: NewSQL | Show results with:NewSQL
  21. [21]
    NewSQL vs Distributed SQL: Know the Differences - YugabyteDB
    Nov 7, 2022 · The shift to the cloud has accelerated over the past few years, partly due to COVID-19 and the demand for hybrid work environments. It is ...
  22. [22]
    [PDF] Distributed Database Systems: The Case for NewSQL - HAL lirmm
    Shared-nothing provides excellent scalability, through scale-out, unlike shared-memory and shared-disk.Missing: benefits | Show results with:benefits
  23. [23]
    [PDF] NewSQL - Brown CS
    Feb 6, 2012 · High per-node performance. • Parallel, shared-nothing architecture. Michael Stonebraker-“New SQL: An Alternative to NoSQLand Old SQL for New ...
  24. [24]
    Consistency and Concurrency in NewSQL Database Systems
    Oct 18, 2024 · Strong Consistency: Strong consistency guarantees that after a write is acknowledged, all subsequent reads will reflect that write. This type of ...Missing: master | Show results with:master
  25. [25]
    None
    ### Summary of ACID Properties in Spanner
  26. [26]
    How CockroachDB does distributed, atomic transactions
    Sep 2, 2015 · Allowing overlapping, concurrent transactions is the “I” in ACID, which guarantees isolation. We'll cover the details of how we accomplish ...Strategy · The Detailed Transaction... · Switch: Cockroachdb...
  27. [27]
    Transactions - CockroachDB
    Each transaction guarantees ACID semantics spanning arbitrary tables and rows, even when data is distributed. If a transaction succeeds, all mutations are ...
  28. [28]
    What is Database Sharding or a Database Shard? - YugabyteDB
    Database sharding is the process of breaking up large database tables into smaller chunks of horizontal data partitions called shards.The Perils Of Manual... · Common Database Sharding... · Geo-Partitioning
  29. [29]
    An Enterprise Architecture Overview - CockroachDB
    Apr 4, 2025 · CockroachDB achieves elastic scalability through its distributed SQL architecture, which enables vertical scaling as well as horizontal ...1. Operational Excellence · 2. Security · Key Architecture Elements Of...
  30. [30]
    How YugabyteDB Scales to More than One Million Inserts Per Second
    Oct 22, 2019 · The YugabyteDB database scales beyond 1M inserts/sec by leveraging sharding and horizontal scaling for rapid data handling.
  31. [31]
    [PDF] VoltDB in-memory DataBase achieVes Best-in-class results, running ...
    this benchmark application does a bit more than ycsB does in each of its transactions, and with 10 server nodes they achieved a rate of about 1.2 million.
  32. [32]
    [PDF] TOP NEWSQL DATABASES AND FEATURES CLASSIFICATION
    Durable Distributed Cache, DDC, involve the power of RDBMs,. ANSI SQL support, ACID transaction, backup, security and administration. At significant peak time ...
  33. [33]
    [PDF] NewSQL: Towards Next-Generation Scalable RDBMS for Online ...
    Transparent clustering/ sharding: These solutions retain the OLTP databases in their original format, but provide a pluggable feature to cluster transparently, ...
  34. [34]
    [PDF] Recent Advances and Benchmarking of NewSQL for OLTP and ...
    Aug 23, 2023 · Hence, this research investigates the use of emerging. NewSQL databases along with Hybrid Transaction and. Analytics Processing (HTAP) which are ...Missing: vectorized | Show results with:vectorized
  35. [35]
    Spanner: TrueTime and external consistency
    This feature of TrueTime is used by Spanner to assign timestamps to transactions. Specifically, every transaction is assigned a timestamp that reflects the ...
  36. [36]
    Spanner innovations in 2024 | Google Cloud Blog
    Dec 21, 2024 · Spanner is Google's always-on, virtually unlimited database that powers planet-scale applications like Gmail, YouTube, and Google Photos.
  37. [37]
    Spanner: Always-on, virtually unlimited scale database | Google Cloud
    Build intelligent apps with a single database that combines relational, graph, key value, and search. No maintenance windows mean uninterrupted apps.Spanner documentation · Pricing · Spanner · Spanner CodelabsMissing: 2025 | Show results with:2025
  38. [38]
    Universal Storage · SingleStore Helios Documentation
    Oct 17, 2024 · Universal storage allows you to support large-scale Online Transaction Processing (OLTP) and Hybrid Transactional and Analytical Processing (HTAP) at a lower ...
  39. [39]
    SingleStoreDB: The Real-Time Analytics Database
    SingleStoreDB is a real-time analytics database that powers interactive, in-app applications. From supply chain analytics to fraud, cybersecurity, ...Application With In-App... · Streaming Data Ingestion · Separation Of Storage And...Missing: memory embeddings 2025
  40. [40]
    Real-Time Enterprise AI - SingleStore
    A database built for AI workloads. No ETL, no complex data pipelines – combine transactions, analytics, and vector search on a single, unified platform. Get ...Missing: memory 2025
  41. [41]
    Made on SingleStore: Customers-Analysts-Partners-Peer Reviews
    ### Summary of SingleStore Key Features
  42. [42]
    Volt Active Data | Data Platform for Mission-Critical Applications
    Streaming Data. Build transactional stream processing applications that ensure correctness, serve requests in under 10 milliseconds, and use minimum resources.Career Opportunities · Without compromising · Developer Edition · CompanyMissing: NewSQL memory OLTP computing
  43. [43]
    Capabilities - Volt Active Data
    Volt Active Data is the leading data platform designed to power real-time telco and other applications that must dynamically react in single-digit milliseconds.Missing: OLTP computing
  44. [44]
    Customers
    ### Summary of VoltDB Features from Customer Page
  45. [45]
    NuoDB: Distributed SQL Database
    ### Summary of NuoDB Features
  46. [46]
    Quick Dive into NuoDB Architecture - 3DS Blog - Dassault Systèmes
    Jul 15, 2021 · NuoDB is a distributed SQL database designed with distributed application deployment challenges in mind. It's a full SQL solution that provides all the ...Missing: polyglot persistence hybrid
  47. [47]
    NEWSQL Database Unlocking Growth Potential - Data Insights Market
    Rating 4.8 (1,980) Nov 1, 2025 · The NewSQL database market is experiencing robust growth, projected to reach an estimated market size of $1500 million by 2025, with a ...
  48. [48]
    Architecture Overview
    ### Summary of CockroachDB Architecture
  49. [49]
    High-Performing Distributed SQL Database - YugabyteDB
    YugabyteDB powers business-critical apps with a resilient, scalable database offering flexible geo-distribution and PostgreSQL-compatible APIs.
  50. [50]
    pingcap/tidb: TiDB - the open-source, cloud-native, distributed SQL ...
    MySQL Compatibility: TiDB is compatible with MySQL 8.0, allowing you to use familiar protocols, frameworks and tools. You can migrate applications to TiDB ...Wiki · Issues 4.1k · Pull requests 1.2k · Actions
  51. [51]
    Exploring TiDB: A Leading Open-Source HTAP Database
    Oct 4, 2024 · At its core, TiDB is an open-source, MySQL-compatible distributed SQL database that excels in both online transactional processing (OLTP) and ...Understanding Tidb In The... · Tidb's Foundations And Open... · Tidb's Role In Cloud-Native...Missing: NewSQL | Show results with:NewSQL
  52. [52]
    VoltDB Open Source / Community Edition - ODBMS.org
    Feb 7, 2020 · VoltDB Community Edition is distributed under AGPL, source code is on GitHub, and can be downloaded from the download page.Missing: IoT | Show results with:IoT
  53. [53]
    Chapter 2. Installing VoltDB
    ### Summary of VoltDB Community Edition
  54. [54]
    What is a Data Platform? - Volt Active Data
    Apr 13, 2021 · Open source data platforms typically promise cost savings, access to an engaged community of contributors, and freedom from vendor lock-in.Key Takeaways · Main Advantages Of A Data... · How To Choose The Best Data...
  55. [55]
    Cloud RDBMS Innovations in 2025:Serverless, Distributed SQL, and ...
    Even open-source–based services are adopting this model: startups ... Distributed SQL (sometimes called NewSQL) ... Cloud database adoption offers compelling ...
  56. [56]
    Open Source Database Software Market Report | Global Forecast ...
    Open Source Database Software Market Report | Global Forecast From 2025 To 2033 ... adoption of NewSQL databases. The choice of ... adoption of open source database ...
  57. [57]
    Fraud Detection at Scale with CockroachDB & AWS AI
    Jul 7, 2025 · CockroachDB uses vector indexing for fast, real-time fraud detection, storing transactions and using AWS AI for training and classifying fraud.
  58. [58]
    Fast Data in Financial Services: Key Trends to Maintain a ...
    Aug 18, 2017 · NewSQL offerings like Volt Active Data offer the best solution for ingesting, analyzing and acting on the massive volumes of real-time data ...
  59. [59]
    CockroachDB for Orders & Inventory Management
    CockroachDB simplifies your architecture with a single logical database to deliver a global view of your ecommerce data.Optimize Ecommerce From... · Capture Global Revenue Year... · Orders & Inventory...
  60. [60]
    Why TiDB Beats Vitess and CockroachDB in Ninja Van on K8s
    After we compared Vitess, CockroachDB (CRDB), and TiDB, an open-source, MySQL-compatible, distributed SQL database, we found that TiDB is an optimal solution.Tidb Test Results · How We're Using Tidb To... · Tidb Operator Auto-Operates...
  61. [61]
    CockroachDB for Healthcare | Use Case Overview
    Build on a cloud foundation that is HIPAA-ready and can be used safely to store protected health information. Support new healthcare application development on ...Healthcare Use Cases · Healthtech Resources · Why Cockroachdb?
  62. [62]
    NewSQL vs NoSQL in the Race to 5G - Volt Active Data
    Jan 15, 2021 · NewSQL combines ACID compliance with the scalability of NoSQL, making it better suited for 5G networks due to its consistency, availability, and ...Missing: queries | Show results with:queries
  63. [63]
    Telecom provider replaces Amazon Aurora with CockroachDB
    For an always-on customer experience, a major US telecom provider switched to CockroachDB.Missing: VoltDB 5G<|separator|>
  64. [64]
    Fast Data is the New Paradigm for IoT Solutions
    May 12, 2016 · Fast Data, spurred by IoT, focuses on real-time data processing for quick, actionable insights, and immediate delivery of results.
  65. [65]
    (PDF) A Comparative Analysis of Relational, NoSQL, and NewSQL ...
    Jul 23, 2024 · This study explores the significant features, the characteristics, the limitations and the companies that used the three known databases.
  66. [66]
    [PDF] NoSQL and NewSQL Databases: Scaling beyond relational limits
    Apr 2, 2025 · This article explores the evolution and capabilities of NoSQL and NewSQL databases as solutions that address the limitations of traditional ...
  67. [67]
    Comparison of SQL, NoSQL and NewSQL databases for internet of ...
    This paper compares the performance of three databases each from the said technologies; SQL (MySQL), NoSQL (MongoDB) and NewSQL (VoltDB) respectively for sensor ...Missing: benchmarks RDBMS