DBMS > Heroic vs. IBM Cloudant vs. LMDB vs. SQLite vs. TerminusDB

System Properties Comparison Heroic vs. IBM Cloudant vs. LMDB vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

A high performant, light-weight, embedded key-value database library

Widely used embeddable, in-process RDBMS

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

Primary database model

Secondary database models

Document store
RDF store

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

github.com/spotify/heroic

www.ibm.com/products/cloudant

www.symas.com/symas-embedded-database-lmdb

www.sqlite.org

terminusdb.com

Technical documentation

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

www.lmdb.tech/doc

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Symas

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2014

2010

2011

2000

2018

Current release

0.9.32, January 2024

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Public Domain

Open Source

GPL V3

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

Java

Erlang

Prolog, Rust

Server operating systems

hosted

Linux
Unix
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

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

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

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

JavaScript
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

Journaling Streams

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

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 for users can be defined per database

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.