DBMS > BoltDB vs. EsgynDB vs. Heroic vs. IBM Cloudant vs. Oracle

System Properties Comparison BoltDB vs. EsgynDB vs. Heroic vs. IBM Cloudant vs. Oracle

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

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

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

github.com/boltdb/bolt

www.esgyn.cn

github.com/spotify/heroic

www.ibm.com/products/cloudant

www.oracle.com/database

Technical documentation

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

Developer

Esgyn

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

Initial release

2013

2015

2014

2010

1980

Current release

23c, September 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

commercial

restricted free version is 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

Java

Erlang

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

hosted

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

Data scheme

schema-free

yes

schema-free

yes

Schemaless in JSON and XML columns

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

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

Java 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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

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

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

atomic operations within a document possible

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

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'

User concepts

Access control

fine grained access rights according to SQL-standard

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.