DBMS > Google Cloud Firestore vs. Kingbase vs. Oracle Berkeley DB vs. Snowflake

System Properties Comparison Google Cloud Firestore vs. Kingbase vs. Oracle Berkeley DB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Widely used in-process key-value store

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

Primary database model

Document store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	0.44
Rank	#258	Overall
	#117	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

firebase.google.com/products/firestore

www.kingbase.com.cn

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

Technical documentation

firebase.google.com/docs/firestore

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Google

BeiJing KINGBASE Information technologies inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Initial release

2017

1999

1994

2014

Current release

V8.0, August 2021

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial license 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 and Java

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Data scheme

schema-free

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

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

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

CLI Client
JDBC
ODBC

Supported programming languages

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

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes, with Cloud Functions

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica 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

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.

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

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.