DBMS > Elasticsearch vs. EXASOL vs. GridGain vs. Snowflake

System Properties Comparison Elasticsearch vs. EXASOL vs. GridGain vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

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

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

Primary database model

Search engine

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.elastic.co/elasticsearch

www.exasol.com

www.gridgain.com

www.snowflake.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.exasol.com/resources

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

Developer

Elastic

Exasol

GridGain Systems, Inc.

Snowflake Computing Inc.

Initial release

2010

2000

2007

2014

Current release

8.6, January 2023

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Elastic License

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

All OS with a Java VM

Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

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

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

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

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

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

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

yes (cache interceptors and events)

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

yes

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Hadoop integration

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

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.

Memcached and Redis integration

yes

User concepts

Access control

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

Security Hooks for custom implementations

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.