DBMS > Datomic vs. Heroic vs. LevelDB vs. OpenSearch vs. ToroDB

System Properties Comparison Datomic vs. Heroic vs. LevelDB vs. OpenSearch vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Vector DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

www.datomic.com

github.com/spotify/heroic

github.com/google/leveldb

github.com/opensearch-project
opensearch.org

github.com/torodb/server

Technical documentation

docs.datomic.com

spotify.github.io/heroic

github.com/google/leveldb/blob/main/doc/index.md

opensearch.org/docs/latest

Developer

Cognitect

Spotify

Google

Amazon Web Services

8Kdata

Initial release

2012

2014

2011

2021

2016

Current release

1.0.6735, June 2023

1.23, February 2021

2.5.0, January 2023

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2.0

Open Source

AGPL-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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java, Clojure

Java

C++

Java

Server operating systems

All OS with a Java VM

Illumos
Linux
OS X
Windows

All OS with a Java VM

All OS with a Java 7 VM

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

Java API
RESTful HTTP/JSON API

Supported programming languages

Clojure
Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

none

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

with automatic compression on writes

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

User concepts

Access control

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.