DBMS > Hyprcubd vs. RocksDB vs. SAP SQL Anywhere vs. Trafodion vs. VoltDB

System Properties Comparison Hyprcubd vs. RocksDB vs. SAP SQL Anywhere vs. Trafodion vs. VoltDB

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

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

Description

Serverless Time Series DBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

hyprcubd.com (offline)

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

trafodion.apache.org

www.voltdb.com

Technical documentation

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

trafodion.apache.org/documentation.html

docs.voltdb.com

Developer

Hyprcubd, Inc.

Facebook, Inc.

SAP

formerly Sybase

Apache Software Foundation, originally developed by HP

VoltDB Inc.

Initial release

2013

1992

2014

2010

Current release

9.2.1, May 2024

17, July 2015

2.3.0, February 2019

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Open Source

Apache 2.0

Open Source

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

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

C++, Java

Java, C++

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

gRPC (https)

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes, in C/C++, Java, .Net or Perl

Java Stored Procedures

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Database mirroring

yes, via HBase

Multi-source replication
Source-replica replication

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

Eventual Consistency

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

yes

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

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

token access

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.