DBMS > Faircom DB vs. Google Cloud Firestore vs. JanusGraph vs. RocksDB

System Properties Comparison Faircom DB vs. Google Cloud Firestore vs. JanusGraph vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store
Relational DBMS

Document store

Graph DBMS

Key-value store

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.faircom.com/products/faircom-db

firebase.google.com/products/firestore

janusgraph.org

rocksdb.org

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

firebase.google.com/docs/firestore

docs.janusgraph.org

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

Google

Linux Foundation; originally developed as Titan by Aurelius

Facebook, Inc.

Initial release

1979

2017

2013

Current release

V12, November 2020

0.6.3, February 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

Open Source

BSD

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

ANSI C, C++

Java

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Linux
OS X
Unix
Windows

Linux

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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.

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

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

Clojure
Java
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

tunable from ACID to Eventually Consistent

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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 with additional protections for files

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

User authentification and security via Rexster Graph Server

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.