DBMS > Cubrid vs. Heroic vs. Percona Server for MongoDB vs. Snowflake vs. TerminusDB

System Properties Comparison Cubrid vs. Heroic vs. Percona Server for MongoDB vs. Snowflake vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

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

Primary database model

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	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

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

github.com/spotify/heroic

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

terminusdb.com

Technical documentation

cubrid.org/manuals

spotify.github.io/heroic

docs.percona.com/percona-distribution-for-mongodb

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

CUBRID Corporation, CUBRID Foundation

Spotify

Percona

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2008

2014

2015

2014

2018

Current release

11.0, January 2021

3.4.10-2.10, November 2017

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

GPL Version 2

commercial

Open Source

GPL V3

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

Java

C++

Prolog, Rust

Server operating systems

Linux
Windows

Linux

hosted

Linux

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

HQL (Heroic Query Language, a JSON-based language)
HTTP API

proprietary protocol using JSON

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Source-replica replication

yes

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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.

yes

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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

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.