DBMS > Amazon Redshift vs. Cloudflare Workers KV vs. EsgynDB vs. Geode vs. Ignite

System Properties Comparison Amazon Redshift vs. Cloudflare Workers KV vs. EsgynDB vs. Geode vs. Ignite

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A global, low-latency, key-value store for applications on Cloudflare with exceptionally high read volumes and low-latency.

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Key-value store
Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.39
Rank	#274	Overall
	#39	Key-value stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

aws.amazon.com/redshift

www.cloudflare.com/developer-platform/workers-kv

www.esgyn.cn

geode.apache.org

ignite.apache.org

Technical documentation

docs.aws.amazon.com/redshift

developers.cloudflare.com/kv/api

geode.apache.org/docs

apacheignite.readme.io/docs

Developer

Amazon (based on PostgreSQL)

Cloudflare

Esgyn

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Initial release

2012

2018

2015

2002

2015

Current release

1.1, February 2017

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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++, Java, .Net

Server operating systems

hosted

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

yes

SQL-like query language (OQL)

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

APIs and other access methods

JDBC
ODBC

HTTP REST
Proprietary protocol

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

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

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

All languages supporting JDBC/ODBC/ADO.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

user defined functions

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

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Multi-source replication

yes (replicated cache)

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

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes, on a single node

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

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.