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

System Properties Comparison Apache Drill vs. Firebase Realtime Database vs. OrientDB 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

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

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Document store
Relational DBMS

Document store

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

drill.apache.org

firebase.google.com/products/realtime-database

orientdb.org

www.snowflake.com

Technical documentation

drill.apache.org/docs

firebase.google.com/docs/database

www.orientdb.com/docs/last/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Google

acquired by Google 2014

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Initial release

2012

2010

2014

Current release

1.20.3, January 2023

3.2.29, March 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache version 2

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

Java

Server operating systems

Linux
OS X
Windows

hosted

All OS with a Java JDK (>= JDK 6)

hosted

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language, no joins

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C++

Java
JavaScript
Objective-C

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

limited functionality with using 'rules'

Java, Javascript

user defined functions

Triggers

Callbacks are triggered when data changes

Hooks

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

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

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

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

yes, based on authentication and database rules

Access rights for users and roles; record level security configurable

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.