DBMS > Apache Druid vs. Axibase vs. Kinetica vs. RocksDB vs. Solr

System Properties Comparison Apache Druid vs. Axibase vs. Kinetica vs. RocksDB vs. Solr

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Fully vectorized database across both GPUs and CPUs

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

druid.apache.org

axibase.com/docs/atsd/finance

www.kinetica.com

rocksdb.org

solr.apache.org

Technical documentation

druid.apache.org/docs/latest/design

docs.kinetica.com

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

Apache Software Foundation and contributors

Axibase Corporation

Kinetica

Facebook, Inc.

Apache Software Foundation

Initial release

2012

2013

2012

2013

2006

Current release

29.0.1, April 2024

15585

7.1, August 2021

8.11.4, April 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

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

commercial

Open Source

BSD

Open Source

Apache Version 2

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

C++

Java

Server operating systems

Linux
OS X
Unix

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

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

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

SQL for querying

SQL-like query language

SQL-like DML and DDL statements

Solr Parallel SQL Interface

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Go
Java
PHP
Python
R
Ruby

C++
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

user defined functions

Java plugins

Triggers

yes

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

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

optimistic locking

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users and roles on table level

yes

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.