DBMS > Cubrid vs. EsgynDB vs. MonetDB vs. OrientDB vs. SQLite

System Properties Comparison Cubrid vs. EsgynDB vs. MonetDB vs. OrientDB vs. SQLite

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

A relational database management system that stores data in columns

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	1.72
Rank	#148	Overall
	#68	Relational DBMS

Score	3.27
Rank	#97	Overall
	#16	Document stores
	#6	Graph DBMS
	#15	Key-value stores

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

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

Technical documentation

cubrid.org/manuals

www.monetdb.org/Documentation

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

Developer

CUBRID Corporation, CUBRID Foundation

Esgyn

MonetDB BV

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2008

2015

2004

2010

2000

Current release

11.0, January 2021

Dec2023 (11.49), December 2023

3.2.29, March 2024

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla Public License 2.0

Open Source

Apache version 2

Open Source

Public Domain

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

C, C++, Java

C++, Java

Java

Server operating systems

Linux
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java JDK (>= JDK 6)

server-less

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

SQL 2003 with some extensions

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes, in SQL, C, R

Java, Javascript

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding via remote tables

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication between multi datacenters

none

Source-replica replication available in experimental status

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

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.