DBMS > EJDB vs. IBM Cloudant vs. Oracle vs. Tkrzw

System Properties Comparison EJDB vs. IBM Cloudant vs. Oracle vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store

Relational DBMS

Key-value store

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

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

github.com/Softmotions/ejdb

www.ibm.com/products/cloudant

www.oracle.com/database

dbmx.net/tkrzw

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

Developer

Softmotions

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

Mikio Hirabayashi

Initial release

2012

2010

1980

2020

Current release

23c, September 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

Erlang

C and C++

C++

Server operating systems

server-less

hosted

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

Linux
macOS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

with proprietary extensions

APIs and other access methods

in-process shared library

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

atomic operations within a document possible

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Optimistic locking

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

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

yes

using specific database classes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.