DBMS > Apache Doris vs. Cachelot.io vs. MySQL vs. Realm vs. Tkrzw

System Properties Comparison Apache Doris vs. Cachelot.io vs. MySQL vs. Realm vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

In-memory caching system

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

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

Technical documentation

github.com/apache/doris/wiki

dev.mysql.com/doc

realm.io/docs

Developer

Apache Software Foundation, originally contributed from Baidu

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

Mikio Hirabayashi

Initial release

2017

2015

1995

2014

2020

Current release

1.2.2, February 2023

8.4.0, April 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Simplified BSD License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.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.

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

Implementation language

Java

C++

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
MySQL client

Memcached protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
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

.Net
Java

with Android only
Objective-C
React Native
Swift

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

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

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 capabilities

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

yes

In-Memory realm

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

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.