DBMS > FoundationDB vs. Hazelcast vs. Oracle vs. OrigoDB vs. Vitess

System Properties Comparison FoundationDB vs. Hazelcast vs. Oracle vs. OrigoDB vs. Vitess

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Ordered key-value store. Core features are complimented by layers.

A widely adopted in-memory data grid

Widely used RDBMS

A fully ACID in-memory object graph database

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/apple/foundationdb

hazelcast.com

www.oracle.com/database

origodb.com

vitess.io

Technical documentation

apple.github.io/foundationdb

hazelcast.org/imdg/docs

docs.oracle.com/en/database

origodb.com/docs

vitess.io/docs

Developer

FoundationDB

Hazelcast

Oracle

Robert Friberg et al

The Linux Foundation, PlanetScale

Initial release

2013

2008

1980

2009

under the name LiveDB

2013

Current release

6.2.28, November 2020

5.3.6, November 2023

23c, September 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

Open Source

Apache Version 2.0, commercial licenses available

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

C and C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

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

Linux
Windows

Docker
Linux
macOS

Data scheme

schema-free

some layers support schemas

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

some layers support typing

yes

User defined using .NET types and collections

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

the object must implement a serialization strategy

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

SQL-like query language

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

.Net

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

in SQL-layer only

yes

Event Listeners, Executor Services

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Events

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication
Source-replica replication

Source-replica replication

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

Linearizable consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

in SQL-layer only

yes

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

isolation level can be parameterized

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Write ahead log

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

Role-based access control

fine grained access rights according to SQL-standard

Role based authorization

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.