DBMS > Cubrid vs. Databricks vs. Ehcache vs. Microsoft Azure Cosmos DB

System Properties Comparison Cubrid vs. Databricks vs. Ehcache vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

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.

A widely adopted Java cache with tiered storage options

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Website

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

www.databricks.com

www.ehcache.org

azure.microsoft.com/services/cosmos-db

Technical documentation

cubrid.org/manuals

docs.databricks.com

www.ehcache.org/documentation

learn.microsoft.com/azure/cosmos-db

Developer

CUBRID Corporation, CUBRID Foundation

Databricks

Terracotta Inc, owned by Software AG

Microsoft

Initial release

2008

2013

2009

2014

Current release

11.0, January 2021

3.10.0, March 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; commercial licenses available

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

C, C++, Java

Java

Server operating systems

Linux
Windows

hosted

All OS with a Java VM

hosted

Data scheme

yes

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

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

with Databricks SQL

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC
RESTful HTTP API

JCache

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

Supported programming languages

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

Python
R
Scala

Java

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

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions and aggregates

JavaScript

Triggers

yes

Cache Event Listeners

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by using Terracotta Server

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

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

using a tiered cache-storage approach

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

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

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.