DBMS > Cubrid vs. FoundationDB vs. GeoMesa vs. SQLite vs. TerminusDB

System Properties Comparison Cubrid vs. FoundationDB vs. GeoMesa vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

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

Ordered key-value store. Core features are complimented by layers.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Spatial DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

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

github.com/apple/foundationdb

www.geomesa.org

www.sqlite.org

terminusdb.com

Technical documentation

cubrid.org/manuals

apple.github.io/foundationdb

www.geomesa.org/documentation/stable/user/index.html

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

CUBRID Corporation, CUBRID Foundation

FoundationDB

CCRi and others

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2008

2013

2014

2000

2018

Current release

11.0, January 2021

6.2.28, November 2020

5.0.0, May 2024

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

Public Domain

Open Source

GPL V3

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

Scala

Prolog, Rust

Server operating systems

Linux
Windows

Linux
OS X
Windows

server-less

Linux

Data scheme

yes

schema-free

some layers support schemas

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

some layers support typing

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

supported in specific SQL layer only

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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
Python

Server-side scripts

Stored procedures

Java Stored Procedures

in SQL-layer only

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

depending on storage layer

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

depending on storage layer

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

depending on storage layer

Foreign keys

Referential integrity

yes

in SQL-layer only

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 journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Role-based access control

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.