DBMS > Cubrid vs. MySQL vs. QuestDB vs. Teradata Aster

System Properties Comparison Cubrid vs. MySQL vs. QuestDB vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Widely used open source RDBMS

A high performance open source SQL database for time series data

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Website

cubrid.com (korean)
cubrid.org (english)

www.mysql.com

questdb.io

Technical documentation

cubrid.org/manuals

dev.mysql.com/doc

questdb.io/docs

Developer

CUBRID Corporation, CUBRID Foundation

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

Teradata

Initial release

2008

1995

2014

2005

Current release

11.0, January 2021

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

commercial

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.

Implementation language

C, C++, Java

C and C++

Java (Zero-GC), C++, Rust

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Data scheme

yes

schema-free via InfluxDB Line Protocol

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL with time-series extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
C++
Go
Java
JavaScript (Node.js)
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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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 for single-table writes

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

through memory mapped files

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.