DBMS > Cubrid vs. FoundationDB vs. Hazelcast vs. Snowflake

System Properties Comparison Cubrid vs. FoundationDB vs. Hazelcast vs. Snowflake

Please select another system to include it in the comparison.

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.

A widely adopted in-memory data grid

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

github.com/apple/foundationdb

hazelcast.com

www.snowflake.com

Technical documentation

cubrid.org/manuals

apple.github.io/foundationdb

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

Developer

CUBRID Corporation, CUBRID Foundation

FoundationDB

Hazelcast

Snowflake Computing Inc.

Initial release

2008

2013

2008

2014

Current release

11.0, January 2021

6.2.28, November 2020

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

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

Java

Server operating systems

Linux
Windows

Linux
OS X
Windows

All OS with a Java VM

hosted

Data scheme

yes

schema-free

some layers support schemas

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

some layers support typing

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.

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

supported in specific SQL layer only

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

in SQL-layer only

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

yes

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

in SQL-layer only

yes

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

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

Role-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.