DBMS > Cubrid vs. EJDB vs. Geode vs. MaxDB

System Properties Comparison Cubrid vs. EJDB vs. Geode vs. MaxDB

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

A robust and reliable RDBMS optimized to run all major SAP solutions

Primary database model

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	2.65
Rank	#111	Overall
	#55	Relational DBMS

Website

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

github.com/Softmotions/ejdb

geode.apache.org

maxdb.sap.com

Technical documentation

cubrid.org/manuals

github.com/Softmotions/ejdb/blob/master/README.md

geode.apache.org/docs

maxdb.sap.com/documentation

Developer

CUBRID Corporation, CUBRID Foundation

Softmotions

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

SAP, acquired from Software AG (Adabas-D) in 1997

Initial release

2008

2012

2002

1984

Current release

11.0, January 2021

1.1, February 2017

7.9.10.12, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Limited community edition free

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

Java

C++

Server operating systems

Linux
Windows

server-less

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

in-process shared library

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

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

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

SAP Content Server High Availability using Amazon EFS and SUSE | Amazon Web Services
30 December 2020, AWS Blog

SAP Aligns Mainstream Maintenance Commitments Across Its Enterprise Solutions
11 August 2020, SAP News

SIOS looks to boost SAP HANA automated replication
29 March 2023, TechTarget

Alibaba Cloud Offers Access to SAP Software for Customers
5 June 2018, Alizila

Your SAP HANA Cheat Sheet: Milestones, Terms and More
14 May 2012, SiliconANGLE News

provided by Google News

Share this page