DBMS > Geode vs. OceanBase vs. OrigoDB vs. PouchDB vs. SQLite

System Properties Comparison Geode vs. OceanBase vs. OrigoDB vs. PouchDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

A distributed, high available RDBMS compatible with Oracle and MySQL

A fully ACID in-memory object graph database

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Document store

Relational DBMS

Secondary database models

Document store
Wide column store

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

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

Score	1.66
Rank	#147	Overall
	#68	Relational DBMS

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

geode.apache.org/docs

en.oceanbase.com/docs/oceanbase-database

origodb.com/docs

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

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

OceanBase

previously Alibaba and Ant Group

Robert Friberg et al

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2002

2010

2009

under the name LiveDB

2012

2000

Current release

1.1, February 2017

4.3.0, April 2024

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Commercial license available

Open Source

Public Domain

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

Java

C++

JavaScript

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
Windows

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

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

can be achieved using .NET

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

.NET Client API
HTTP API
LINQ

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

.Net

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

yes

View functions in JavaScript

Triggers

yes

Cache Event Listeners

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

horizontal partitioning

client side managed; servers are not synchronized

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Write ahead log

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Access rights per client and object definable

Access rights for users, groups and roles according to SQL-standard

Role based authorization

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.