DBMS > Amazon Redshift vs. EsgynDB vs. Geode vs. Spark SQL vs. Trafodion

System Properties Comparison Amazon Redshift vs. EsgynDB vs. Geode vs. Spark SQL vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

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	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

geode.apache.org/docs

spark.apache.org/docs/latest/sql-programming-guide.html

trafodion.apache.org/documentation.html

Developer

Amazon (based on PostgreSQL)

Esgyn

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

Apache Software Foundation

Apache Software Foundation, originally developed by HP

Initial release

2012

2015

2002

2014

Current release

1.1, February 2017

3.5.0 ( 2.13), September 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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

Scala

C++, Java

Server operating systems

hosted

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Linux

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (OQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

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

Java
Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

user defined functions

Java Stored Procedures

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Multi-source replication

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

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

fine grained access rights according to SQL-standard

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.