DBMS > Machbase Neo vs. SAP HANA vs. SwayDB vs. VoltDB vs. XTDB

System Properties Comparison Machbase Neo vs. SAP HANA vs. SwayDB vs. VoltDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

TimeSeries DBMS for AIoT and BigData

In-memory, column based data store. Available as appliance or cloud service

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

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

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational 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

machbase.com

www.sap.com/products/hana.html

swaydb.simer.au

www.voltdb.com

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

Technical documentation

Developer

Machbase

SAP

Simer Plaha

VoltDB Inc.

Juxt Ltd.

Initial release

2013

2010

2018

2010

2019

Current release

V8.0, August 2023

2.0 SPS07 (April 4, 2023), April 2023

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

commercial

free test version available

commercial

Open Source

GNU Affero GPL V3.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

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Java, C++

Clojure

Server operating systems

Linux
macOS
Windows

Appliance or cloud-service

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

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

SQLScript, R

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

yes

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.