DBMS > Cubrid vs. DolphinDB vs. Machbase Neo vs. Vitess

System Properties Comparison Cubrid vs. DolphinDB vs. Machbase Neo 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

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

TimeSeries DBMS for AIoT and BigData

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

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

www.dolphindb.com

machbase.com

vitess.io

Technical documentation

cubrid.org/manuals

docs.dolphindb.cn/en/help200/index.html

machbase.com/dbms

vitess.io/docs

Developer

CUBRID Corporation, CUBRID Foundation

DolphinDB, Inc

Machbase

The Linux Foundation, PlanetScale

Initial release

2008

2018

2013

Current release

11.0, January 2021

v2.00.4, January 2022

V8.0, August 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free community version available

commercial

free test version 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

C++

Server operating systems

Linux
Windows

Linux
macOS
Windows

Docker
Linux
macOS

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

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

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Administrators, Users, Groups

simple password-based access control

Users with fine-grained authorization concept

no user groups or 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page