DBMS > Apache Drill vs. Citus vs. Firebase Realtime Database vs. Snowflake

System Properties Comparison Apache Drill vs. Citus vs. Firebase Realtime Database vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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.

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	2.13
Rank	#117	Overall
	#56	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

drill.apache.org

www.citusdata.com

firebase.google.com/products/realtime-database

www.snowflake.com

Technical documentation

drill.apache.org/docs

docs.citusdata.com

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Google

acquired by Google 2014

Snowflake Computing Inc.

Initial release

2012

2010

2012

2014

Current release

1.20.3, January 2023

8.1, December 2018

License

Commercial or Open Source

Open Source

Apache Version 2

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
OS X
Windows

Linux

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

standard, with numerous extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C++

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

Java
JavaScript
Objective-C

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'

user defined functions

Triggers

yes

Callbacks are triggered when data changes

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

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.