DBMS > Cubrid vs. Databricks vs. Datomic vs. DuckDB vs. RocksDB

System Properties Comparison Cubrid vs. Databricks vs. Datomic vs. DuckDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

An embeddable, in-process, column-oriented SQL OLAP RDBMS

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

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key-value store

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.57
Rank	#74	Overall
	#40	Relational DBMS

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

Website

cubrid.com (korean)
cubrid.org (english)

Technical documentation

github.com/facebook/rocksdb/wiki

Developer

CUBRID Corporation, CUBRID Foundation

Databricks

Cognitect

Facebook, Inc.

Initial release

2008

2013

2012

2018

2013

Current release

11.0, January 2021

1.0.6735, June 2023

0.10, February 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

MIT License

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

Java, Clojure

C++

Server operating systems

Linux
Windows

hosted

All OS with a Java VM

server-less

Linux

Data scheme

yes

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

yes

with Databricks SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Python
R
Scala

Clojure
Java

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions and aggregates

yes

Transaction Functions

Triggers

yes

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

But extensive use of caching in the application peers

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.