DBMS > ClickHouse vs. Graph Engine vs. Informix vs. MySQL vs. TerminusDB

System Properties Comparison ClickHouse vs. Graph Engine vs. Informix vs. MySQL 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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

Document store
Spatial DBMS

Document store
RDF store

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	17.12
Rank	#34	Overall
	#21	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

clickhouse.com

www.graphengine.io

www.ibm.com/products/informix

www.mysql.com

terminusdb.com

Technical documentation

clickhouse.com/docs

www.graphengine.io/docs/manual

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

Clickhouse Inc.

Microsoft

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2016

2010

1984

1995

2018

Current release

v24.4.1.2088-stable, May 2024

14.10.FC5, November 2020

8.4.0, April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MIT License

commercial

free developer edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
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.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

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

Implementation language

C++

.NET and C

C, C++ and Java

C and C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
macOS

.NET

AIX
HP-UX
Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Since Version 12.10 support for JSON/BSON datatypes

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

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

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

RESTful HTTP API

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

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

C#
C++
F#
Visual Basic

.Net
C
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

horizontal partitioning

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 authentication, authorization, and auditing controls

Users with fine-grained authorization concept

no user groups or roles

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.