DBMS > EsgynDB vs. RocksDB vs. RRDtool vs. Teradata

System Properties Comparison EsgynDB vs. RocksDB vs. RRDtool vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

www.esgyn.cn

rocksdb.org

oss.oetiker.ch/rrdtool

www.teradata.com

Technical documentation

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

docs.teradata.com

Developer

Esgyn

Facebook, Inc.

Tobias Oetiker

Teradata

Initial release

2015

2013

1999

1984

Current release

8.11.4, April 2024

1.8.0, 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

commercial

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.

Implementation language

C++, Java

C++

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

Server operating systems

Linux

HP-UX
Linux

hosted
Linux

Data scheme

yes

schema-free

yes

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

in-process shared library
Pipes

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

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.