DBMS > Apache IoTDB vs. Kinetica vs. RavenDB vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Apache IoTDB vs. Kinetica vs. RavenDB vs. RocksDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Fully vectorized database across both GPUs and CPUs

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

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

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

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

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

docs.kinetica.com

ravendb.net/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Kinetica

Hibernating Rhinos

Facebook, Inc.

SAP

formerly Sybase

Initial release

2018

2012

2010

2013

1992

Current release

1.1.0, April 2023

7.1, August 2021

5.4, July 2022

9.2.1, May 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL version 3, commercial license available

Open Source

BSD

commercial

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

Java

C, C++

C++

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

Linux
macOS
Raspberry Pi
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL-like DML and DDL statements

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
Native API

JDBC
ODBC
RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C++
Java
JavaScript (Node.js)
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions

yes

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

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Source-replica replication

Multi-source replication

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency or Eventual Consistency depending on configuration

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

User concepts

Access control

yes

Access rights for users and roles on table level

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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.