DBMS > GBase vs. Geode vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison GBase vs. Geode vs. Oracle Berkeley DB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Widely used in-process key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

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

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.gbase.cn

geode.apache.org

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

Technical documentation

geode.apache.org/docs

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

General Data Technology Co., Ltd.

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

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2004

2002

1994

2013

Current release

GBase 8a, GBase 8s, GBase 8c

1.1, February 2017

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

commercial license available

Open Source

BSD

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, Java, Python

Java

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

SQL-like query language (OQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica 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

yes

Concurrency

Support for concurrent manipulation of data

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

yes

Access rights per client and object definable

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.