DBMS > IBM Db2 warehouse vs. MySQL vs. TerminusDB vs. Tigris

System Properties Comparison IBM Db2 warehouse vs. MySQL vs. TerminusDB vs. Tigris

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud-based data warehousing service

Widely used open source RDBMS

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

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

www.ibm.com/products/db2/warehouse

www.mysql.com

terminusdb.com

www.tigrisdata.com

Technical documentation

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

www.tigrisdata.com/docs

Developer

IBM

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Tigris Data, Inc.

Initial release

2014

1995

2018

2022

Current release

8.3.0, January 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

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

C and C++

Prolog, Rust

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Linux
macOS
Windows

Data scheme

yes

Typing

predefined data types such as float or date

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

Java
JavaScript (Node.js)
Perl
PHP
Python
R
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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

PL/SQL, SQL PL

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Journaling Streams

yes

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

in-memory journaling

yes, using FoundationDB

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

no user groups or roles

Role-based access control

Access rights for users and roles

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.