DBMS > EventStoreDB vs. GBase vs. IBM Cloudant vs. Oracle vs. Vitess

System Properties Comparison EventStoreDB vs. GBase vs. IBM Cloudant vs. Oracle vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
Spatial DBMS

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

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	1.11
Rank	#173	Overall
	#78	Relational DBMS

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

www.eventstore.com

www.gbase.cn

www.ibm.com/products/cloudant

www.oracle.com/database

vitess.io

Technical documentation

developers.eventstore.com

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

vitess.io/docs

Developer

Event Store Limited

General Data Technology Co., Ltd.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

The Linux Foundation, PlanetScale

Initial release

2012

2004

2010

1980

2013

Current release

21.2, February 2021

GBase 8a, GBase 8s, GBase 8c

23c, September 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

commercial

restricted free version is available

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, Java, Python

Erlang

C and C++

Server operating systems

Linux
Windows

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

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

Standard with numerous extensions

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

user defined functions

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

isolation level can be parameterized

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

yes

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.