DBMS > Cubrid vs. mSQL vs. SQLite vs. TerarkDB vs. TimescaleDB

System Properties Comparison Cubrid vs. mSQL vs. SQLite vs. TerarkDB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used embeddable, in-process RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

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

hughestech.com.au/products/msql

www.sqlite.org

github.com/bytedance/terarkdb

www.timescale.com

Technical documentation

cubrid.org/manuals

www.sqlite.org/docs.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.timescale.com

Developer

CUBRID Corporation, CUBRID Foundation

Hughes Technologies

Dwayne Richard Hipp

ByteDance, originally Terark

Timescale

Initial release

2008

1994

2000

2016

2017

Current release

11.0, January 2021

4.4, October 2021

3.45.3 (15 April 2024), April 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free licenses can be provided

Open Source

Public Domain

commercial

restricted open source version available

Open Source

Apache 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++

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

server-less

Linux
OS X
Windows

Data scheme

yes

dynamic column types

schema-free

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.