DBMS > Apache Doris vs. Infobright vs. MySQL vs. SAP IQ vs. Tarantool

System Properties Comparison Apache Doris vs. Infobright vs. MySQL vs. SAP IQ vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Widely used open source RDBMS

Columnar RDBMS optimized for Big Data analytics

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

column-oriented

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.64
Rank	#108	Overall
	#52	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

ignitetech.com/softwarelibrary/infobrightdb

www.mysql.com

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.tarantool.io

Technical documentation

github.com/apache/doris/wiki

dev.mysql.com/doc

help.sap.com/docs/SAP_IQ

www.tarantool.io/en/doc

Developer

Apache Software Foundation, originally contributed from Baidu

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SAP, formerly Sybase

Initial release

2017

2005

1995

1994

2008

Current release

1.2.2, February 2023

8.4.0, April 2024

16.1 SPS04, April 2019

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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 MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

Linux

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
MySQL client

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC
RESTful HTTP API

Open binary protocol

Supported programming languages

Java

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

C
C#
C++
Java
Perl
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

shared disk or shared nothing architectures with SAP IQ Multiplexer

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

SAP/Sybase Replication Server

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.