DBMS > Apache Druid vs. GridGain vs. HugeGraph vs. Snowflake

System Properties Comparison Apache Druid vs. GridGain vs. HugeGraph vs. Snowflake

Please select another system to include it in the comparison.

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

GridGain is an in-memory computing platform, built on Apache Ignite

A fast-speed and highly-scalable Graph DBMS

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

Primary database model

Relational DBMS
Time Series DBMS

Key-value store
Relational DBMS

Graph DBMS

Relational DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

druid.apache.org

www.gridgain.com

github.com/hugegraph
hugegraph.apache.org

www.snowflake.com

Technical documentation

druid.apache.org/docs/latest/design

www.gridgain.com/docs/index.html

hugegraph.apache.org/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

GridGain Systems, Inc.

Baidu

Snowflake Computing Inc.

Initial release

2012

2007

2018

2014

Current release

29.0.1, April 2024

GridGain 8.5.1

0.9

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache Version 2.0

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

Java, C++, .Net

Java

Server operating systems

Linux
OS X
Unix

Linux
OS X
Solaris
Windows

Linux
macOS
Unix

hosted

Data scheme

yes

schema-less columns are supported

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

also supports composite index and range index

SQL

Support of SQL

SQL for querying

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Java API
RESTful HTTP API
TinkerPop Gremlin

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Groovy
Java
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

asynchronous Gremlin script jobs

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes (replicated cache)

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

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

Security Hooks for custom implementations

Users, roles and permissions

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.