DBMS > Databricks vs. Drizzle vs. Hawkular Metrics vs. KairosDB vs. RocksDB

System Properties Comparison Databricks vs. Drizzle vs. Hawkular Metrics vs. KairosDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Distributed Time Series DBMS based on Cassandra or H2

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Key-value store

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

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

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

Website

www.databricks.com

www.hawkular.org

github.com/kairosdb/kairosdb

rocksdb.org

Technical documentation

docs.databricks.com

www.hawkular.org/hawkular-metrics/docs/user-guide

kairosdb.github.io

github.com/facebook/rocksdb/wiki

Developer

Databricks

Drizzle project, originally started by Brian Aker

Community supported by Red Hat

Facebook, Inc.

Initial release

2013

2008

2014

2013

Current release

7.2.4, September 2012

1.2.2, November 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

BSD

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

C++

Java

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
OS X
Windows

Linux

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

HTTP REST

Graphite protocol
HTTP REST
Telnet API

C++ API
Java API

Supported programming languages

Python
R
Scala

C
C++
Java
PHP

Go
Java
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

Triggers

hooks for callbacks inside the server can be used.

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

based on Cassandra

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.