DBMS > Datomic vs. EXASOL vs. RRDtool vs. Snowflake vs. Tkrzw

System Properties Comparison Datomic vs. EXASOL vs. RRDtool vs. Snowflake vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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.

Cloud-based data warehousing service for structured and semi-structured data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.datomic.com

www.exasol.com

oss.oetiker.ch/rrdtool

www.snowflake.com

dbmx.net/tkrzw

Technical documentation

docs.datomic.com

www.exasol.com/resources

oss.oetiker.ch/rrdtool/doc

docs.snowflake.net/manuals/index.html

Developer

Cognitect

Exasol

Tobias Oetiker

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2012

2000

1999

2014

2020

Current release

1.0.7075, December 2023

1.8.0, 2022

0.9.3, August 2020

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GPL V2 and FLOSS

commercial

Open Source

Apache Version 2.0

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

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

C++

Server operating systems

All OS with a Java VM

HP-UX
Linux

hosted

Linux
macOS

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

in-process shared library
Pipes

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
Java

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

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

using specific database classes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.