DBMS > Apache IoTDB vs. Coveo vs. Hyprcubd vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Apache IoTDB vs. Coveo vs. Hyprcubd vs. RocksDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

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

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

Primary database model

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

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

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

iotdb.apache.org

www.coveo.com

hyprcubd.com (offline)

rocksdb.org

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

Technical documentation

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

docs.coveo.com

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Coveo

Hyprcubd, Inc.

Facebook, Inc.

SAP

formerly Sybase

Initial release

2018

2012

2013

1992

Current release

1.1.0, April 2023

9.2.1, May 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD

commercial

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

Java

C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

APIs and other access methods

JDBC
Native API

RESTful HTTP API

gRPC (https)

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
Java
JavaScript
Python

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

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

yes

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

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

User concepts

Access control

yes

granular access controls, API key management, content filters

token access

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.