DBMS > Google Cloud Firestore vs. Riak TS vs. Tkrzw vs. XTDB

System Properties Comparison Google Cloud Firestore vs. Riak TS vs. Tkrzw vs. XTDB

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.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

firebase.google.com/products/firestore

dbmx.net/tkrzw

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

firebase.google.com/docs/firestore

www.tiot.jp/riak-docs/riak/ts/latest

www.xtdb.com/docs

Developer

Google

Open Source, formerly Basho Technologies

Mikio Hirabayashi

Juxt Ltd.

Initial release

2017

2015

2020

2019

Current release

3.0.0, September 2022

0.9.3, August 2020

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

MIT License

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

Erlang

C++

Clojure

Server operating systems

hosted

Linux
OS X

Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes, limited

limited SQL, making use of Apache Calcite

APIs and other access methods

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

HTTP API
Native Erlang Interface

HTTP REST
JDBC

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++
Java
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Erlang

Triggers

yes, with Cloud Functions

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google launches Cloud Firestore, a new document database for app developers
3 October 2017, TechCrunch

Google's Cloud-Native NoSQL Database Cloud Firestore Is Now Generally Available
8 February 2019, InfoQ.com

Firestore and Python | NoSQL on Google Cloud
7 August 2020, Towards Data Science

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page