DBMS > ClickHouse vs. MySQL vs. RRDtool vs. SAP Adaptive Server vs. TerminusDB

System Properties Comparison ClickHouse vs. MySQL vs. RRDtool vs. SAP Adaptive Server vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Widely used open source RDBMS

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.

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Graph DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Spatial DBMS

with Boeing's Spatial Query Server

Document store
RDF store

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

clickhouse.com

www.mysql.com

oss.oetiker.ch/rrdtool

www.sap.com/products/technology-platform/sybase-ase.html

terminusdb.com

Technical documentation

clickhouse.com/docs

dev.mysql.com/doc

oss.oetiker.ch/rrdtool/doc

help.sap.com/docs/SAP_ASE

terminusdb.github.io/terminusdb/#

Developer

Clickhouse Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Tobias Oetiker

SAP, Sybase

DataChemist Ltd.

Initial release

2016

1995

1999

1987

2018

Current release

v24.4.1.2088-stable, May 2024

8.4.0, April 2024

1.8.0, 2022

16.0

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V2 and FLOSS

commercial

Open Source

GPL V3

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

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

C and C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
macOS

FreeBSD
Linux
OS X
Solaris
Windows

HP-UX
Linux

AIX
HP-UX
Linux
Solaris
Unix
Windows

Linux

Data scheme

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.

yes

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

with proprietary extensions

yes

SQL-like query language (WOQL)

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

in-process shared library
Pipes

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

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
Java
Perl
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Java and Transact-SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

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

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Role-based access control

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.