DBMS > Cubrid vs. Geode vs. Graph Engine vs. jBASE

System Properties Comparison Cubrid vs. Geode vs. Graph Engine vs. jBASE

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

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A robust multi-value DBMS comprising development tools and middleware

Primary database model

Relational DBMS

Key-value store

Graph DBMS
Key-value store

Multivalue DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Website

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

geode.apache.org

www.graphengine.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

cubrid.org/manuals

geode.apache.org/docs

www.graphengine.io/docs/manual

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

CUBRID Corporation, CUBRID Foundation

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

Microsoft

Rocket Software (formerly Zumasys)

Initial release

2008

2002

2010

1991

Current release

11.0, January 2021

1.1, February 2017

5.7

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

MIT License

commercial

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

.NET and C

Server operating systems

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

.NET

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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)

Embedded SQL for jBASE in BASIC

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

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

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

C#
C++
F#
Visual Basic

.Net
Basic
Jabbascript
Java

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

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.

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

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

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

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

provided by Google News

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

Share this page