DBMS > Apache Druid vs. EXASOL vs. Google Cloud Firestore vs. Snowflake vs. WakandaDB

System Properties Comparison Apache Druid vs. EXASOL vs. Google Cloud Firestore vs. Snowflake vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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.

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS
Time Series DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.10
Rank	#356	Overall
	#17	Object oriented DBMS

Website

druid.apache.org

www.exasol.com

firebase.google.com/products/firestore

www.snowflake.com

wakanda.github.io

Technical documentation

druid.apache.org/docs/latest/design

www.exasol.com/resources

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

wakanda.github.io/doc

Developer

Apache Software Foundation and contributors

Exasol

Google

Snowflake Computing Inc.

Wakanda SAS

Initial release

2012

2000

2017

2014

2012

Current release

29.0.1, April 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

AGPLv3, extended commercial license available

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

C++, JavaScript

Server operating systems

Linux
OS X
Unix

hosted

Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

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

yes

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 for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

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

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

user defined functions

yes

Triggers

yes

yes, with Cloud Functions

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users, groups and roles according to SQL-standard

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

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

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.