DBMS > Cubrid vs. etcd vs. Google Cloud Firestore vs. MySQL vs. PostGIS

System Properties Comparison Cubrid vs. etcd vs. Google Cloud Firestore vs. MySQL vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

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

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.

Widely used open source RDBMS

Spatial extension of PostgreSQL

Primary database model

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

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

etcd.io
github.com/etcd-io/etcd

firebase.google.com/products/firestore

www.mysql.com

postgis.net

Technical documentation

cubrid.org/manuals

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

firebase.google.com/docs/firestore

dev.mysql.com/doc

postgis.net/documentation

Developer

CUBRID Corporation, CUBRID Foundation

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

2017

1995

2005

Current release

11.0, January 2021

3.4, August 2019

8.4.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++, Java

C and C++

Server operating systems

Linux
Windows

FreeBSD
Linux
Windows

experimental

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC
JSON over HTTP

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes, Firebase Rules & Cloud Functions

yes

proprietary syntax

user defined functions

Triggers

yes

yes, watching key changes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

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

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

no user groups or roles

yes

based on PostgreSQL

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.