DBMS > GBase vs. Google BigQuery vs. Google Cloud Firestore vs. Ignite vs. Tkrzw

System Properties Comparison GBase vs. Google BigQuery vs. Google Cloud Firestore vs. Ignite vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Large scale data warehouse service with append-only tables

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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Document store

Key-value store
Relational DBMS

Key-value store

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.gbase.cn

cloud.google.com/bigquery

firebase.google.com/products/firestore

ignite.apache.org

dbmx.net/tkrzw

Technical documentation

cloud.google.com/bigquery/docs

firebase.google.com/docs/firestore

apacheignite.readme.io/docs

Developer

General Data Technology Co., Ltd.

Google

Apache Software Foundation

Mikio Hirabayashi

Initial release

2004

2010

2017

2015

2020

Current release

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 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, Java, Python

C++, Java, .Net

C++

Server operating systems

Linux

hosted

Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

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

Standard with numerous extensions

yes

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, Firebase Rules & Cloud Functions

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes, with Cloud Functions

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes (compute grid and hadoop accelerator)

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

Since BigQuery is designed for querying 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

using specific database classes

User concepts

Access control

yes

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

Security Hooks for custom implementations

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.