DBMS > Apache Phoenix vs. Heroic vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Apache Phoenix vs. Heroic vs. RocksDB vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

phoenix.apache.org

github.com/spotify/heroic

rocksdb.org

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

Technical documentation

phoenix.apache.org

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Spotify

Facebook, Inc.

SAP

formerly Sybase

Initial release

2014

2013

1992

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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++

Server operating systems

Linux
Unix
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.