DBMS > Citus vs. Firebase Realtime Database vs. jBASE vs. Snowflake

System Properties Comparison Citus vs. Firebase Realtime Database vs. jBASE vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

A robust multi-value DBMS comprising development tools and middleware

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

Primary database model

Secondary database models

Document store

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

Score	2.13
Rank	#117	Overall
	#56	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.citusdata.com

firebase.google.com/products/realtime-database

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.snowflake.com

Technical documentation

docs.citusdata.com

firebase.google.com/docs/database

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.snowflake.net/manuals/index.html

Developer

Google

acquired by Google 2014

Rocket Software (formerly Zumasys)

Snowflake Computing Inc.

Initial release

2010

2012

1991

2014

Current release

8.1, December 2018

5.7

License

Commercial or Open Source

Open Source

AGPL, commercial license also 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

Server operating systems

Linux

hosted

AIX
Linux
Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

optional

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
JavaScript
Objective-C

.Net
Basic
Jabbascript
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

limited functionality with using 'rules'

yes

user defined functions

Triggers

yes

Callbacks are triggered when data changes

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Access rights can be defined down to the item level

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.