DBMS > Apache Druid vs. FatDB vs. Google Cloud Datastore vs. Heroic

System Properties Comparison Apache Druid vs. FatDB vs. Google Cloud Datastore vs. Heroic

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Primary database model

Relational DBMS
Time Series DBMS

Document store
Key-value store

Document store

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Website

druid.apache.org

cloud.google.com/datastore

github.com/spotify/heroic

Technical documentation

druid.apache.org/docs/latest/design

cloud.google.com/datastore/docs

spotify.github.io/heroic

Developer

Apache Software Foundation and contributors

FatCloud

Google

Spotify

Initial release

2012

2008

2014

Current release

29.0.1, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache 2.0

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
Unix

Windows

hosted

Data scheme

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

via Elasticsearch

SQL

Support of SQL

SQL for querying

Via inetgration in SQL Server

SQL-like query language (GQL)

APIs and other access methods

JDBC
RESTful HTTP/JSON API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

using Google App Engine

Triggers

yes

via applications

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

selectable replication factor

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

User concepts

Access control

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

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Apache Druid Wins Best Big Data Product in the 2023 BigDATAwire Readers' Choice Awards
26 January 2024, Datanami

'Lucifer' Botnet Turns Up the Heat on Apache Hadoop Servers
21 February 2024, Dark Reading

New DDoS malware Attacking Apache big-data stack, Hadoop, & Druid Servers
26 February 2024, GBHackers

Apache Druid Takes Its Place In The Pantheon Of Databases
16 June 2022, The Next Platform

How to connect DataGrip to Apache Druid | by Zisis Flokas
18 October 2021, Towards Data Science

provided by Google News

Best cloud storage of 2024
4 June 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page