DBMS > Cubrid vs. Dolt vs. JaguarDB vs. SQLite

System Properties Comparison Cubrid vs. Dolt vs. JaguarDB vs. SQLite

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Performant, highly scalable DBMS for AI and IoT applications

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

github.com/dolthub/dolt
www.dolthub.com

www.jaguardb.com

www.sqlite.org

Technical documentation

cubrid.org/manuals

docs.dolthub.com

www.jaguardb.com/support.html

www.sqlite.org/docs.html

Developer

CUBRID Corporation, CUBRID Foundation

DoltHub Inc

DataJaguar, Inc.

Dwayne Richard Hipp

Initial release

2008

2018

2015

2000

Current release

11.0, January 2021

3.3 July 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

GPL V3.0

Open Source

Public Domain

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

the server part. Clients available in other languages

Server operating systems

Linux
Windows

Linux
macOS
Windows

Linux

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

CLI Client
HTTP REST

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

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

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

currently in alpha release

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

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

Only one user is configurable, and must be specified in the config file at startup

rights management via user accounts

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.