DBMS > Apache Kylin vs. HEAVY.AI vs. Kinetica vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison Apache Kylin vs. HEAVY.AI vs. Kinetica vs. Oracle Berkeley DB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

Widely used in-process key-value store

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

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

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

Website

kylin.apache.org

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

Technical documentation

kylin.apache.org/docs

docs.heavy.ai

docs.kinetica.com

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation, originally contributed from eBay Inc

HEAVY.AI, Inc.

Kinetica

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2015

2016

2012

1994

2013

Current release

3.1.0, July 2020

5.10, January 2022

7.1, August 2021

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

commercial license available

Open Source

BSD

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

C, C++

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

yes

SQL-like DML and DDL statements

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

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

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.