DBMS > Postgres-XL vs. Quasardb vs. TerarkDB vs. VoltDB

System Properties Comparison Postgres-XL vs. Quasardb vs. TerarkDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Distributed, high-performance timeseries database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.postgres-xl.org

quasar.ai

github.com/bytedance/terarkdb

www.voltdb.com

Technical documentation

www.postgres-xl.org/documentation

doc.quasar.ai/master

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.voltdb.com

Developer

quasardb

ByteDance, originally Terark

VoltDB Inc.

Initial release

2014

since 2012, originally named StormDB

2009

2016

2010

Current release

10 R1, October 2018

3.14.1, January 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Mozilla public license

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

restricted open source version available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java, C++

Server operating systems

Linux
macOS

BSD
Linux
OS X
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

XML type, but no XML query functionality

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

distributed, parallel query execution

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

consistent hashing

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with selectable replication factor

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

MVCC

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using LevelDB

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

Users and roles with access to stored procedures

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Hubble Unexpectedly Finds Double Quasar in Distant Universe
4 October 2023, Science@NASA

Record quasar is most luminous object in the universe
20 February 2024, EarthSky

Quasar Partners with PTC to Empower IoT Customers with High-Performance Data Solutions
11 September 2023, Datanami

Meet the NiceGUI: Your Soon-to-be Favorite Python UI Library
16 April 2024, Towards Data Science

QUASAR yacht (Bilgin, 46.8m, 2016)
3 July 2023, Boat International

provided by Google News

A Chinese company is making the cloud 200x faster · TechNode
3 July 2017, TechNode

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page