DBMS > Coveo vs. Datomic vs. EsgynDB vs. RocksDB vs. RRDtool

System Properties Comparison Coveo vs. Datomic vs. EsgynDB vs. RocksDB vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

oss.oetiker.ch/rrdtool

Technical documentation

docs.coveo.com

docs.datomic.com

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

Developer

Coveo

Cognitect

Esgyn

Facebook, Inc.

Tobias Oetiker

Initial release

2012

2015

2013

1999

Current release

1.0.7075, December 2023

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

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, Clojure

C++, Java

C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

All OS with a Java VM

Linux

HP-UX
Linux

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

C++ API
Java API

in-process shared library
Pipes

Supported programming languages

C#
Java
JavaScript
Python

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
Perl
Python
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

Java Stored Procedures

Triggers

yes

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

yes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

Multi-source replication between multi datacenters

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

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

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

yes

User concepts

Access control

granular access controls, API key management, content filters

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.