DBMS > Cubrid vs. Fauna vs. Heroic vs. Snowflake vs. Spark SQL

System Properties Comparison Cubrid vs. Fauna vs. Heroic vs. Snowflake vs. Spark SQL

Editorial information provided by DB-Engines

Name

Description

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

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Time Series DBMS

Relational DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.52
Rank	#153	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

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

fauna.com

github.com/spotify/heroic

www.snowflake.com

spark.apache.org/sql

Technical documentation

cubrid.org/manuals

docs.fauna.com

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

CUBRID Corporation, CUBRID Foundation

Fauna, Inc.

Spotify

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2008

2014

Current release

11.0, January 2021

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache 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

Scala

Java

Scala

Server operating systems

Linux
Windows

hosted

Linux
OS X
Windows

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

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API

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

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

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

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

consistent hashing

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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 capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Identity management, authentication, and 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.