DBMS > Cubrid vs. Derby vs. Geode vs. Machbase Neo vs. MySQL

System Properties Comparison Cubrid vs. Derby vs. Geode vs. Machbase Neo vs. MySQL

Editorial information provided by DB-Engines

Name

Description

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

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

Technical documentation

cubrid.org/manuals

db.apache.org/derby/manuals/index.html

geode.apache.org/docs

machbase.com/dbms

dev.mysql.com/doc

Developer

CUBRID Corporation, CUBRID Foundation

Apache Software Foundation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

1997

2002

2013

1995

Current release

11.0, January 2021

10.17.1.0, November 2023

1.1, February 2017

V8.0, August 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free test version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++, Java

Java

C and C++

Server operating systems

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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

SQL-like query language (OQL)

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Java

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes, on a single node

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

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.