DBMS > Amazon Redshift vs. EsgynDB vs. GridGain vs. Lovefield vs. MySQL

System Properties Comparison Amazon Redshift vs. EsgynDB vs. GridGain vs. Lovefield vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Embeddable relational database for web apps written in pure JavaScript

Widely used open source RDBMS

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/redshift

www.esgyn.cn

www.gridgain.com

google.github.io/lovefield

www.mysql.com

Technical documentation

docs.aws.amazon.com/redshift

www.gridgain.com/docs/index.html

github.com/google/lovefield/blob/master/docs/spec_index.md

dev.mysql.com/doc

Developer

Amazon (based on PostgreSQL)

Esgyn

GridGain Systems, Inc.

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2015

2007

2014

1995

Current release

GridGain 8.5.1

2.1.12, February 2017

9.0.0, July 2024

License

Commercial or Open Source

commercial

commercial, open source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C++, Java

Java, C++, .Net, Python, REST, SQL

JavaScript

C and C++

Server operating systems

hosted

Linux

Linux
OS X
Solaris
Windows
z/OS

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

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

SQL-like query language

via JavaScript builder pattern

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

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

yes

proprietary syntax

Triggers

yes (cache interceptors and events)

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

yes (replicated cache)

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control
Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

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.