VoltDB

From Wikipedia, the free encyclopedia
Volt Active Data
Developer(s)Volt Active Data
Initial releaseMay 25, 2010 (2010-05-25)
Stable release
11.3 / April 21, 2022; 23 months ago (2022-04-21)
Repository
Written inJava, C++
Operating systemLinux, macOS
PlatformJava
TypeRDBMS
LicenseGNU Affero General Public License v3, VoltDB Proprietary License
Websitevoltactivedata.com

Volt Active Data (formerly VoltDB) is an in-memory database designed by Michael Stonebraker, Sam Madden, and Daniel Abadi.

It is an ACID-compliant RDBMS that uses a shared-nothing architecture, and is derived from work done by Stonebraker on OLTP system performance[1] and optimization.[2]

It is available in both enterprise and community editions. The community edition is licensed under the GNU Affero General Public License.

Architecture[edit]

VoltDB is a NewSQL OLTP[3] relational database that supports SQL access from within pre-compiled Java stored procedures.

While direct SQL access is supported,[4] the most efficient form of interaction is using stored procedure calls,[5] as it involves fewer network trips. Stored procedures are written in Java by extending a class called VoltProcedure' and implementing a ‘run()’ method that includes both SQL statements and supporting Java logic. Internally data is managed by a C++ core to avoid garbage collection issues.[6]

VoltDB relies on horizontal partitioning down to the individual hardware thread to scale, k-safety (synchronous replication) to provide high availability, and a combination of continuous snapshots and command logging for durability (crash recovery).

VoltDB is based on H-Store. It uses a shared-nothing architecture to scale. Data and the processing associated with it are distributed across the CPU cores within the servers composing a single VoltDB cluster. By extending its shared-nothing foundation to the per-core level, VoltDB scales with the increasing core-per-CPU counts on multi-core servers.

By making stored procedures the unit of transaction and executing them at the partition containing the necessary data, it is possible to eliminate round trip messaging between SQL statements. Stored procedures are executed serially and to completion in a single thread without locking or latching, similar to the LMAX architecture.[7] Because data is in memory and local to the partition, a stored procedure can execute in microseconds. VoltDB's stored procedure initiation scheme allows all nodes to initiate stored procedures while avoiding a single serializable global order.[8]

VoltDB is ACID compliant. Data is written to durable storage. Durability is ensured by continuous snapshots; asynchronous command logging, which creates both snapshots and a log of transactions between snapshots; and synchronous command logging, which logs transactions after the transaction completes and before it is committed to the database. This ensures that no transactions are committed that are not logged and that no transactions are lost.

History[edit]

VoltDB v5.0 introduced a database monitoring and management tool, the VoltDB Management Center (VMC for short). VMC provides browser-based one-stop monitoring and configuration management of the VoltDB database, including graphs for cluster throughput and latency as well as CPU and memory usage for the current server.

VoltDB version 5.1, released in March 2015, introduced database replication (DR) functionality, removing any single point of failure. DR provides simultaneous, parallel replication of multiple partitions and binary logs of transaction results, saving the replica from having to replay the transaction.

V6.0 [9] introduced geospatial datatypes

V6.1 [10] added streams, which can be inserted into, with support for aggregation in materialized views on the streaming data,.

V6.6 [11] added support for XDCR running clusters between mixed versions of Volt and of mixed sizes and configurations.

V7.1[12] , released in March 2017 introduced support for TLS encryption for client networking.

V7.5[13] released July 28, 2017 introduced the kafkaloader, for consuming streaming events from Kafka directly into a database table or into a stored procedure for processing.

V7.6[14] (August 28, 2017) introduced User-Defined SQL Functions, allowing customers to write custom functions in Java and make them callable from a SQL statement. V8.0[15] (February 6, 2018) introduced TLS encryption for networking between clusters using DR and XDCR and for intra-cluster communication.

V8.2[16] (July 12, 2018) introduced the TTL feature that allows applications to define a "time to live" on timestamp column in a table. Once the expiration time is hit, an internal process cleans up the records from the database.

V8.4[17] (December 29, 2018) introduced Long-Term Supported versions to Volt customers. This version increases the support from one year to three years, allowing customers to stay on a version and receive critical updates for stability, security and correctness. V9.0[18] (April 11, 2019) introduced new streaming functionality, including migration of data to a stream upon expiration and change-data capture.

V9.3[19] (May 1, 2020), a Long-Term Supported (LTS) release, introduced Scheduled Tasks, a way to automate repetitive tasks and procedure calls from within Volt. Schedule Tasks has an easy to use interface for calling pre-defined procedures and can also be fully customized in Java to create more complex schedules.

V10.0[20] (August, 2020) introduced a Volt Operator for Kubernetes and Helm Charts offering a complete solution for running VoltDB databases in a Kubernetes cloud environment. In addition V10.0 provided a Prometheus agent for collection and graphing of metrics.

V10.2[21] (January 2021) introduced VoltDB Topics to provide the intelligent streaming of VoltDB's existing import and export capabilities, but with the flexibility of Kafka-like streams. Topics allow for both inbound and outbound streaming to multiple client producers and consumers. They allow for intelligent processing and manipulation of the data as it passes through the pipeline. V10.2 is a LTS release.

V11.0[22] (April 21, 2022) introduces connectivity to DataDog, support for Java 17, compatibility with Kubernetes 22.0 and priority transactions.

In February 2022 the product was renamed to "Volt Active Data".[23]

See also[edit]

References[edit]

  1. ^ "OLTP Through the Looking Glass, and What We Found There" (PDF). nms.csail.mit.edu.
  2. ^ "The End of an Architectural Era (It's Time for a Complete Rewrite)" (PDF). nms.csail.mit.edu.
  3. ^ "High Performance RDBMS for Fast Data Applications Requiring Smart Streaming with Transactions" (PDF). voltdb.com.
  4. ^ "JDBC Interface". voltdb.com.
  5. ^ "Designing Stored Procedures to Access the Database". voltdb.com.
  6. ^ "Debunking Myths About the VoltDB In-Memory Database - DZone Java". dzone.com. Retrieved 2020-11-13.
  7. ^ "The LMAX Architecture". martinfowler.com. Retrieved 2019-04-07.
  8. ^ "DB Developer Central". VoltDB. Retrieved 2019-04-07.
  9. ^ "VoltDB 6 Release Notes". voltactivedata.com.
  10. ^ "VoltDB 6 Release Notes". voltactivedata.com.
  11. ^ "VoltDB 6 Release Notes". voltactivedata.com.
  12. ^ "VoltDB 7 Release Notes". voltactivedata.com.
  13. ^ "VoltDB 7 Release Notes". voltactivedata.com.
  14. ^ "VoltDB 7 Release Notes". voltactivedata.com.
  15. ^ "VoltDB 8 Release Notes". voltactivedata.com.
  16. ^ "VoltDB 8 Release Notes". voltactivedata.com.
  17. ^ "VoltDB 8 Release Notes". voltactivedata.com.
  18. ^ "VoltDB 9 Release Notes". voltactivedata.com.
  19. ^ "VoltDB 9 Release Notes". voltactivedata.com.
  20. ^ "VoltDB 10 Release Notes". voltactivedata.com.
  21. ^ "VoltDB 10 Release Notes". voltactivedata.com.
  22. ^ "VoltDB 10 Release Notes". voltactivedata.com.
  23. ^ "As of today, we are Volt Active Data". voltactivedata.com.

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=VoltDB&oldid=1140817035"