DBMS > Apache Druid vs. Cubrid vs. IBM Cloudant vs. JaguarDB vs. SQLite

System Properties Comparison Apache Druid vs. Cubrid vs. IBM Cloudant vs. JaguarDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Database as a Service offering based on Apache CouchDB

Performant, highly scalable DBMS for AI and IoT applications

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Document store

Key-value store
Vector DBMS

Relational DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

druid.apache.org

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

www.ibm.com/products/cloudant

www.jaguardb.com

www.sqlite.org

Technical documentation

druid.apache.org/docs/latest/design

cubrid.org/manuals

cloud.ibm.com/docs/Cloudant

www.jaguardb.com/support.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

CUBRID Corporation, CUBRID Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

DataJaguar, Inc.

Dwayne Richard Hipp

Initial release

2012

2008

2010

2015

2000

Current release

29.0.1, April 2024

11.0, January 2021

3.3 July 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2.0

commercial

Open Source

GPL V3.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C, C++, Java

Erlang

C++

the server part. Clients available in other languages

Server operating systems

Linux
OS X
Unix

Linux
Windows

hosted

Linux

server-less

Data scheme

yes

schema-less columns are supported

yes

schema-free

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

SQL for querying

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

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.