DBMS > Amazon Redshift vs. Datomic vs. Ehcache vs. GridGain

System Properties Comparison Amazon Redshift vs. Datomic vs. Ehcache 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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A widely adopted Java cache with tiered storage options

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

Primary database model

Relational DBMS

Key-value store

Key-value store
Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Website

aws.amazon.com/redshift

www.datomic.com

www.ehcache.org

www.gridgain.com

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

www.ehcache.org/documentation

www.gridgain.com/docs/index.html

Developer

Amazon (based on PostgreSQL)

Cognitect

Terracotta Inc, owned by Software AG

GridGain Systems, Inc.

Initial release

2012

2009

2007

Current release

1.0.6735, June 2023

3.10.0, March 2022

GridGain 8.5.1

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

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, Clojure

Java

Java, C++, .Net

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

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

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JCache

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

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

Java

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

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

Triggers

By using transaction functions

yes

Cache Event Listeners

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

by using Terracotta Server

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

recommended only for testing and development

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.