DBMS > Datomic vs. MySQL vs. OpenEdge vs. RRDtool

System Properties Comparison Datomic vs. MySQL vs. OpenEdge vs. RRDtool

Please select another system to include it in the comparison.

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

Widely used open source RDBMS

Application development environment with integrated database management system

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

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

www.datomic.com

www.mysql.com

www.progress.com/openedge

oss.oetiker.ch/rrdtool

Technical documentation

docs.datomic.com

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

oss.oetiker.ch/rrdtool/doc

Developer

Cognitect

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

Tobias Oetiker

Initial release

2012

1995

1984

1999

Current release

1.0.6735, June 2023

8.3.0, January 2024

OpenEdge 12.2, March 2020

1.8.0, 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL V2 and FLOSS

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 MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, Clojure

C and C++

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

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

HP-UX
Linux

Data scheme

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.

yes

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

in-process shared library
Pipes

Supported programming languages

Clojure
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Progress proprietary ABL (Advanced Business Language)

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

yes

proprietary syntax

yes

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Users and groups

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.