DBMS > Apache Kylin vs. EsgynDB vs. RocksDB vs. RRDtool vs. SiteWhere

System Properties Comparison Apache Kylin vs. EsgynDB vs. RocksDB vs. RRDtool vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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.

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

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

Score	1.25
Rank	#170	Overall
	#77	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

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

kylin.apache.org

www.esgyn.cn

rocksdb.org

oss.oetiker.ch/rrdtool

github.com/sitewhere/sitewhere

Technical documentation

kylin.apache.org/docs

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation, originally contributed from eBay Inc

Esgyn

Facebook, Inc.

Tobias Oetiker

SiteWhere

Initial release

2015

2013

1999

2010

Current release

3.1.0, July 2020

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

Open Source

Common Public Attribution License Version 1.0

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

Java

C++, Java

C++

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

Java

Server operating systems

Linux

HP-UX
Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

predefined scheme

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

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

C++ API
Java API

in-process shared library
Pipes

HTTP REST

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

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

none

selectable replication factor

based on HBase

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

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

Users with fine-grained authorization concept

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.