DBMS > Axibase vs. Microsoft Azure Cosmos DB vs. Newts vs. RocksDB vs. Tkrzw

System Properties Comparison Axibase vs. Microsoft Azure Cosmos DB vs. Newts vs. RocksDB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS based on Cassandra

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

axibase.com/docs/atsd/finance

azure.microsoft.com/services/cosmos-db

opennms.github.io/newts

rocksdb.org

dbmx.net/tkrzw

Technical documentation

learn.microsoft.com/azure/cosmos-db

github.com/OpenNMS/newts/wiki

github.com/facebook/rocksdb/wiki

Developer

Axibase Corporation

Microsoft

OpenNMS Group

Facebook, Inc.

Mikio Hirabayashi

Initial release

2013

2014

2013

2020

Current release

15585

8.11.4, April 2024

0.9.3, August 2020

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2.0

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

Linux

hosted

Linux
OS X
Windows

Linux

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

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

HTTP REST
Java API

C++ API
Java API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

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

Java

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

selectable replication factor

based on Cassandra

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

using specific database classes

User concepts

Access control

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.