DBMS > Cubrid vs. GreptimeDB vs. MySQL vs. Vitess

System Properties Comparison Cubrid vs. GreptimeDB vs. MySQL vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An open source Time Series DBMS built for increased scalability, high performance and efficiency

Widely used open source RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	0.09
Rank	#343	Overall
	#31	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

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

greptime.com

www.mysql.com

vitess.io

Technical documentation

Developer

CUBRID Corporation, CUBRID Foundation

Greptime Inc.

Oracle

since 2010, originally MySQL AB, then Sun

The Linux Foundation, PlanetScale

Initial release

2008

2022

1995

2013

Current release

11.0, January 2021

9.0.0, July 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0, commercial licenses 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.

Implementation language

C, C++, Java

Rust

C and C++

Server operating systems

Linux
Windows

Android
Docker
FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free, schema definition possible

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC
HTTP API
JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C++
Erlang
Go
Java
JavaScript

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

Server-side scripts

Stored procedures

Java Stored Procedures

Python

yes

proprietary syntax

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

fine grained access rights according to SQL-standard

Simple rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

GreptimeDB is a SQL & Python-enabled timeseries database system built from scratch...
» more

Competitive advantages

- Inherits advantages of Rust, such as excellent performance, memory safe, resource...
» more

Typical application scenarios

For IoT industries, GreptimeDB can seamless integrate with message queues and other...
» more

Key customers

Greptime's clients span multiple sectors including IoT, connected vehicles, and energy...
» more

Market metrics

GreptimeDB has garnered global recognition by topping GitHub trends following its...
» more

Licensing and pricing models

GreptimeDB: open source, distributed, cloud-native TSDB; supports Hybrid Time-series...
» more

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.