DBMS > Cubrid vs. Firebase Realtime Database vs. SQLite vs. WakandaDB vs. Warp 10

System Properties Comparison Cubrid vs. Firebase Realtime Database vs. SQLite vs. WakandaDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Widely used embeddable, in-process RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

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

firebase.google.com/products/realtime-database

www.sqlite.org

wakanda.github.io

www.warp10.io

Technical documentation

cubrid.org/manuals

firebase.google.com/docs/database

www.sqlite.org/docs.html

wakanda.github.io/doc

www.warp10.io/content/02_Getting_started

Developer

CUBRID Corporation, CUBRID Foundation

Google

acquired by Google 2014

Dwayne Richard Hipp

Wakanda SAS

SenX

Initial release

2008

2012

2000

2012

2015

Current release

11.0, January 2021

3.46.0 (23 May 2024), May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

Open Source

AGPLv3, extended commercial license available

Open Source

Apache License 2.0

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

C, C++, Java

C++, JavaScript

Java

Server operating systems

Linux
Windows

hosted

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Java
JavaScript
Objective-C

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

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

limited functionality with using 'rules'

yes

WarpScript

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

yes, based on authentication and database rules

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.