DBMS > Apache Druid vs. EJDB vs. GridGain vs. SAP IQ vs. Snowflake

System Properties Comparison Apache Druid vs. EJDB vs. GridGain vs. SAP IQ vs. Snowflake

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Columnar RDBMS optimized for Big Data analytics

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

Primary database model

Relational DBMS
Time Series DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

column-oriented

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	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

druid.apache.org

github.com/Softmotions/ejdb

www.gridgain.com

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

Technical documentation

druid.apache.org/docs/latest/design

github.com/Softmotions/ejdb/blob/master/README.md

www.gridgain.com/docs/index.html

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

Softmotions

GridGain Systems, Inc.

SAP, formerly Sybase

Snowflake Computing Inc.

Initial release

2012

2007

1994

2014

Current release

29.0.1, April 2024

GridGain 8.5.1

16.1 SPS04, April 2019

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPLv2

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

Server operating systems

Linux
OS X
Unix

server-less

Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

schema-less columns are supported

schema-free

yes

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

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

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

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

in-process shared library

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

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

user defined functions

Triggers

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

yes (replicated cache)

SAP/Sybase Replication Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

fine grained access rights according to SQL-standard

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.