DBMS > Cubrid vs. EXASOL vs. Google Cloud Datastore vs. SQLite vs. YottaDB

System Properties Comparison Cubrid vs. EXASOL vs. Google Cloud Datastore vs. SQLite vs. YottaDB

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used embeddable, in-process RDBMS

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

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

www.exasol.com

cloud.google.com/datastore

www.sqlite.org

yottadb.com

Technical documentation

cubrid.org/manuals

www.exasol.com/resources

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

yottadb.com/resources/documentation

Developer

CUBRID Corporation, CUBRID Foundation

Exasol

Google

Dwayne Richard Hipp

YottaDB, LLC

Initial release

2008

2000

2008

2000

2001

Current release

11.0, January 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

Open Source

AGPL 3.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

Server operating systems

Linux
Windows

hosted

server-less

Docker
Linux

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

by using the Octo plugin

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

.Net
JDBC
ODBC
WebSocket

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

Java
Lua
Python
R

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

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

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

optimistic locking

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

Access rights for users, groups and roles according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users and groups based on OS-security mechanisms

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.