DBMS > Apache Phoenix vs. Kinetica vs. LevelDB vs. MaxDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Phoenix vs. Kinetica vs. LevelDB vs. MaxDB vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

A robust and reliable RDBMS optimized to run all major SAP solutions

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS
Time Series DBMS

Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

phoenix.apache.org

www.kinetica.com

github.com/google/leveldb

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

Technical documentation

phoenix.apache.org

docs.kinetica.com

github.com/google/leveldb/blob/main/doc/index.md

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Kinetica

Google

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

Initial release

2014

2012

2011

1984

2014

Current release

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

7.1, August 2021

1.23, February 2021

7.9.10.12, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD

commercial

Limited community edition free

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

C++

Server operating systems

Linux
Unix
Windows

Linux

Illumos
Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL-like query language

APIs and other access methods

JDBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C#
Java
Perl
PHP
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions

yes

JavaScript

Triggers

yes

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

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

none

Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

User concepts

Access control

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

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Access rights can be defined down to the item 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.