NewSQL
NewSQL is a class of relational database management systems that seek to provide the scalability of NoSQL systems for online transaction processing (OLTP) workloads while maintaining the ACID guarantees of a traditional database system. Many enterprise systems that handle high-profile data (e.g., financial and order processing systems) are too large for conventional relational databases, but have transactional and consistency requirements that are not practical for NoSQL systems. The only options previously available for these organizations were to either purchase more powerful computers or to develop custom middleware that distributes requests over conventional DBMS. Both approaches feature high infrastructure costs and/or development costs. NewSQL systems attempt to reconcile the conflicts.
NewSQL is a class of relational database management systems that seek to provide the scalability of NoSQL systems for online transaction processing (OLTP) workloads while maintaining the ACID guarantees of a traditional database system.[1][2][3][4]
Many enterprise systems that handle high-profile data (e.g., financial and order processing systems) are too large for conventional relational databases, but have transactional 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 custom middleware that distributes requests over conventional DBMS. Both approaches feature high infrastructure costs and/or development costs. NewSQL systems attempt to reconcile the conflicts.
History
[edit]The term was first used by 451 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 the H-Store parallel database system.[7][8]
Applications
[edit]Typical applications are characterized by heavy OLTP transaction volumes. OLTP transactions;
- are short-lived (i.e., no user stalls)
- touch small amounts of data per transaction
- use indexed lookups (no table scans)
- have a small number of forms (a small number of queries with different arguments).[9]
However, some support hybrid transactional/analytical processing (HTAP) applications. Such systems improve performance and scalability by omitting heavyweight recovery or concurrency control.[10]
List of NewSQL-databases
[edit]- Apache Trafodion
- Clustrix
- CockroachDB
- Couchbase
- CrateDB
- Google Spanner
- MySQL Cluster
- NuoDB
- OceanBase
- Pivotal GemFire XD
- SequoiaDB
- SingleStore was formerly known as MemSQL.
- TIBCO Active Spaces
- TiDB
- TokuDB
- TransLattice Elastic Database
- VoltDB
- YDB
- YugabyteDB
Features
[edit]The two common distinguishing features of NewSQL database solutions are that they support online scalability of NoSQL databases and the relational data model (including ACID consistency) using SQL as their primary interface.[11]
NewSQL systems can be loosely grouped into three categories:[2][12]
New architectures
[edit]NewSQL systems adopt various internal architectures. Some systems employ a cluster of shared-nothing nodes, in which each node manages a subset of the data. They include components such as distributed concurrency control, flow control, and distributed query processing.
SQL engines
[edit]The second category are optimized storage engines for SQL. These systems provide the same programming interface as SQL, but scale better than built-in engines.
Transparent sharding
[edit]These systems automatically split databases across multiple nodes using Raft or Paxos consensus algorithm.
See also
[edit]- Transaction processing
- Partition (database)
- Distributed Relational Database Architecture
- Distributed SQL
References
[edit]- ^ Aslett, Matthew (2011). "How Will The Database Incumbents Respond To NoSQL And NewSQL?" (PDF). 451 Group (published April 4, 2011). Retrieved February 22, 2020.
- ^ a b Pavlo, Andrew; Aslett, Matthew (2016). "What's Really New with NewSQL?" (PDF). SIGMOD Record. Retrieved February 22, 2020.
- ^ Stonebraker, Michael (June 16, 2011). "NewSQL: An Alternative to NoSQL and Old SQL for New OLTP Apps". Communications of the ACM Blog. Retrieved February 22, 2020.
- ^ Hoff, Todd (September 24, 2012). "Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In". Retrieved February 22, 2020.
- ^ a b Aslett, Matthew (April 6, 2011). "What we talk about when we talk about NewSQL". 451 Group. Archived from the original on June 14, 2020. Retrieved February 22, 2020.
- ^ Lloyd, Alex (2012). "Building Spanner" (PDF). Berlin Buzzwords (published June 5, 2012). Retrieved February 22, 2020.
- ^ Aslett, Matthew (March 4, 2008). "Is H-Store the future of database management systems?". Archived from the original on December 7, 2019. Retrieved February 22, 2020.
- ^ Monash, Curt (February 20, 2008). "H-Store: Complete destruction of the old DBMS order?". ZDNet. Retrieved February 22, 2020.
- ^ Stonebraker, Michael; et al. (2007). "The End of an Architectural Era (It's Time for a Complete Rewrite)" (PDF). VLDB '07: Proceedings of the 33rd international conference on Very large data bases. Vienna, Austria. Retrieved February 22, 2020.
- ^ Stonebraker, Michael; Cattell, R. (2011). "10 rules for scalable performance in 'simple operation' datastores". Communications of the ACM. 54 (6): 72. doi:10.1145/1953122.1953144.
- ^ Cattell, R. (2011). "Scalable SQL and NoSQL data stores" (PDF). ACM SIGMOD Record. 39 (4): 12–27. CiteSeerX 10.1.1.692.2621. doi:10.1145/1978915.1978919. S2CID 3357124. Retrieved February 22, 2020.
- ^ Venkatesh, Prasanna (January 30, 2012). "NewSQL - The New Way to Handle Big Data". Retrieved February 22, 2020.
| Types | |
|---|---|
| Concepts | |
| Objects | |
| Components | |
| Functions | |
| Related topics | |
