DBMS > Cubrid vs. Dgraph vs. Google Cloud Firestore vs. Snowflake

System Properties Comparison Cubrid vs. Dgraph vs. Google Cloud Firestore vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed and scalable native Graph DBMS

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

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

Primary database model

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

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

dgraph.io

firebase.google.com/products/firestore

www.snowflake.com

Technical documentation

cubrid.org/manuals

dgraph.io/docs

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

Developer

CUBRID Corporation, CUBRID Foundation

Dgraph Labs, Inc.

Google

Snowflake Computing Inc.

Initial release

2008

2016

2017

2014

Current release

11.0, January 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

Server operating systems

Linux
Windows

Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

yes

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

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

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication via Raft

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.