DBMS > Cubrid vs. EDB Postgres vs. Geode vs. MySQL vs. SiteWhere

System Properties Comparison Cubrid vs. EDB Postgres vs. Geode vs. MySQL vs. SiteWhere

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 EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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

Widely used open source RDBMS

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

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	1.91
Rank	#130	Overall
	#60	Relational DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

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

www.enterprisedb.com

geode.apache.org

www.mysql.com

github.com/sitewhere/sitewhere

Technical documentation

cubrid.org/manuals

www.enterprisedb.com/docs

geode.apache.org/docs

dev.mysql.com/doc

sitewhere1.sitewhere.io/index.html

Developer

CUBRID Corporation, CUBRID Foundation

EnterpriseDB

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

Oracle

since 2010, originally MySQL AB, then Sun

SiteWhere

Initial release

2008

2005

2002

1995

2010

Current release

11.0, January 2021

14, December 2021

1.1, February 2017

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

BSD for PostgreSQL-components

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Common Public Attribution License Version 1.0

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++

Java

Server operating systems

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

predefined scheme

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like query language (OQL)

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

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

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

.Net
All JVM based languages
C++
Groovy
Java
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

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

by hash, list or range

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

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

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

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.