DBMS > Cubrid vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. mSQL vs. Spark SQL

System Properties Comparison Cubrid vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. mSQL vs. Spark SQL

Editorial information provided by DB-Engines

Name

Description

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Globally distributed, horizontally scalable, multi-model database service

mSQL (Mini SQL) is a simple and lightweight RDBMS

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

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	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

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

www.esgyn.cn

azure.microsoft.com/services/cosmos-db

hughestech.com.au/products/msql

spark.apache.org/sql

Technical documentation

cubrid.org/manuals

learn.microsoft.com/azure/cosmos-db

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

CUBRID Corporation, CUBRID Foundation

Esgyn

Microsoft

Hughes Technologies

Apache Software Foundation

Initial release

2008

2015

2014

1994

2014

Current release

11.0, January 2021

4.4, October 2021

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free licenses can be provided

Open Source

Apache 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

C, C++, Java

C++, Java

Scala

Server operating systems

Linux
Windows

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

yes

SQL

Support of SQL

yes

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC

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

JDBC
ODBC

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

C
C++
Delphi
Java
Perl
PHP
Tcl

Java
Python
R
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

In-memory capabilities

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

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

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.