DBMS > Amazon Redshift vs. Badger vs. Elasticsearch vs. GridGain

System Properties Comparison Amazon Redshift vs. Badger vs. Elasticsearch vs. GridGain

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

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

Primary database model

Relational DBMS

Key-value store

Search engine

Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	135.35
Rank	#7	Overall
	#1	Search engines

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

Website

aws.amazon.com/redshift

github.com/dgraph-io/badger

www.elastic.co/elasticsearch

www.gridgain.com

Technical documentation

docs.aws.amazon.com/redshift

godoc.org/github.com/dgraph-io/badger

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

www.gridgain.com/docs/index.html

Developer

Amazon (based on PostgreSQL)

DGraph Labs

Elastic

GridGain Systems, Inc.

Initial release

2012

2017

2010

2007

Current release

8.6, January 2023

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

hosted

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

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

restricted

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

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

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

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

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

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

Triggers

yes

by using the 'percolation' feature

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

informational only, not enforced by the system

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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.