NewSQL is a class ofrelationaldatabase management systems that seek to provide the scalability ofNoSQL systems foronline transaction processing (OLTP) workloads while maintaining theACID guarantees of a traditional database system.[1][2][3][4]
Manyenterprise systems that handle high-profile data (e.g., financial and order processing systems) are too large for conventional relational databases, but havetransactional and consistency requirements that are not practical for NoSQL systems.[5][6] The only options previously available for these organizations were to either purchase more powerful computers or to develop custommiddleware that distributes requests over conventionalDBMS. Both approaches feature high infrastructure costs and/or development costs. NewSQL systems attempt to reconcile the conflicts.
The term was first used by451 Group analyst Matthew Aslett in a 2011 research paper discussing the rise of a new generation of database management systems.[5] One of the first NewSQL systems was theH-Storeparallel database system.[7][8]
Typical applications are characterized by heavyOLTP transaction volumes. OLTP transactions;
However, some supporthybrid transactional/analytical processing (HTAP) applications. Such systems improve performance and scalability by omitting heavyweightrecovery orconcurrency control.[10]
The two common distinguishing features of NewSQL database solutions are that they support online scalability of NoSQL databases and therelational data model (including ACID consistency) usingSQL as their primary interface.[11]
NewSQL systems can be loosely grouped into three categories:[2][12]
NewSQL systems adopt various internal architectures. Some systems employ a cluster ofshared-nothing nodes, in which each node manages a subset of the data. They include components such asdistributed concurrency control, flow control, and distributed query processing.
The second category are optimizedstorage engines forSQL. These systems provide the same programming interface as SQL, but scale better than built-in engines.
These systems automatically split databases across multiple nodes usingRaft orPaxos consensus algorithm.
| Types | |
|---|---|
| Concepts | |
| Objects | |
| Components | |
| Functions | |
| Related topics | |
