DBMS > Machbase Neo vs. SwayDB vs. Trafodion vs. VoltDB vs. XTDB

System Properties Comparison Machbase Neo vs. SwayDB vs. Trafodion vs. VoltDB vs. XTDB

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

TimeSeries DBMS for AIoT and BigData

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Transactional SQL-on-Hadoop DBMS

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

machbase.com/dbms

trafodion.apache.org/documentation.html

docs.voltdb.com

www.xtdb.com/docs

Developer

Machbase

Simer Plaha

Apache Software Foundation, originally developed by HP

VoltDB Inc.

Juxt Ltd.

Initial release

2013

2018

2014

2010

2019

Current release

V8.0, August 2023

2.3.0, February 2019

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

commercial

free test version available

Open Source

GNU Affero GPL V3.0

Open Source

Apache 2.0

Open Source

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

Open Source

MIT License

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

Scala

C++, Java

Java, C++

Clojure

Server operating systems

Linux
macOS
Windows

Linux

Linux
OS X

for development

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Java
Kotlin
Scala

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

Java Stored Procedures

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes, via HBase

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

Atomic execution of operations

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

simple password-based access control

fine grained access rights according to SQL-standard

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

SQL-on-Hadoop Database Trafodion Bridges Transactions and Analysis
24 January 2018, The New Stack

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

Low-latency, distributed database architectures are critical for emerging fog applications
16 July 2022, Embedded Computing Design

provided by Google News

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

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

VoltDB Aims for Fast Big Data Development -- ADTmag
29 January 2015, ADT Magazine

Stonebraker Seeks to Invert the Computing Paradigm with DBOS
12 March 2024, Datanami

provided by Google News

Share this page