DBMS > MySQL vs. OpenMLDB vs. Quasardb vs. STSdb

System Properties Comparison MySQL vs. OpenMLDB vs. Quasardb vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

An open-source machine learning database that provides a feature platform for training and inference

Distributed, high-performance timeseries database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.02
Rank	#367	Overall
	#37	Time Series DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.mysql.com

openmldb.ai

quasar.ai

github.com/STSSoft/STSdb4

Technical documentation

dev.mysql.com/doc

openmldb.ai/docs/zh/main

doc.quasar.ai/master

Developer

Oracle

since 2010, originally MySQL AB, then Sun

4 Paradigm Inc.

quasardb

STS Soft SC

Initial release

1995

2020

2009

2011

Current release

8.4.0, April 2024

2024-2 February 2024

3.14.1, January 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

GPLv2, commercial license available

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

C and C++

C++, Java, Scala

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux

BSD
Linux
OS X
Windows

Windows

Data scheme

yes

Fixed schema

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

yes

primitive types and user defined types (classes)

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

with tags

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
SQLAlchemy

HTTP API

.NET Client API

Supported programming languages

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

C++
Go
Java
Python
Scala

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C#
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.