DBMS > Cubrid vs. Memcached vs. MySQL vs. RisingWave

System Properties Comparison Cubrid vs. Memcached vs. MySQL vs. RisingWave

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

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Relational DBMS

Key-value store

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	16.84
Rank	#32	Overall
	#4	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.61
Rank	#237	Overall
	#111	Relational DBMS

Website

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

www.memcached.org

www.mysql.com

www.risingwave.com/database

Technical documentation

cubrid.org/manuals

github.com/memcached/memcached/wiki

dev.mysql.com/doc

docs.risingwave.com/docs/current/intro

Developer

CUBRID Corporation, CUBRID Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

RisingWave Labs

Initial release

2008

2003

1995

2022

Current release

11.0, January 2021

1.6.29, June 2024

9.0.0, July 2024

1.2, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

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.

Implementation language

C, C++, Java

C and C++

Rust

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Standard SQL-types and JSON

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

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
PostgreSQL wire protocol

Supported programming languages

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

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

UDFs in Python or Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

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

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

Users and 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.