DBMS > BigchainDB vs. Ehcache vs. Oracle vs. TerminusDB

System Properties Comparison BigchainDB vs. Ehcache vs. Oracle vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

A widely adopted Java cache with tiered storage options

Widely used RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

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
RDF store

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.bigchaindb.com

www.ehcache.org

www.oracle.com/database

terminusdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.ehcache.org/documentation

docs.oracle.com/en/database

terminusdb.github.io/terminusdb/#

Developer

Terracotta Inc, owned by Software AG

Oracle

DataChemist Ltd.

Initial release

2016

2009

1980

2018

Current release

3.10.0, March 2022

23c, September 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

Open Source

GPL V3

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

Python

Java

C and C++

Prolog, Rust

Server operating systems

Linux

All OS with a Java VM

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

Linux

Data scheme

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

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

CLI Client
RESTful HTTP API

JCache

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Java

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

JavaScript
Python

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding, horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

using a tiered cache-storage approach

yes

in-memory journaling

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'

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Role-based access control

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.