DBMS > Blueflood vs. Cubrid vs. MySQL vs. Typesense

System Properties Comparison Blueflood vs. Cubrid vs. MySQL vs. Typesense

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Widely used open source RDBMS

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	0.06
Rank	#352	Overall
	#36	Time Series DBMS

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.80
Rank	#209	Overall
	#14	Search engines

Website

blueflood.io

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

www.mysql.com

typesense.org

Technical documentation

github.com/rax-maas/blueflood/wiki

cubrid.org/manuals

dev.mysql.com/doc

typesense.org/docs

Developer

Rackspace

CUBRID Corporation, CUBRID Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2008

1995

2015

Current release

11.0, January 2021

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

Java

C, C++, Java

C and C++

C++

Server operating systems

Linux
OS X

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

predefined scheme

yes

schema-free

pre-defined schema optional

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

APIs and other access methods

HTTP REST

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

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

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

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.