DBMS > Amazon DynamoDB vs. EXASOL vs. GeoSpock vs. Trafodion

System Properties Comparison Amazon DynamoDB vs. EXASOL vs. GeoSpock vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Spatial and temporal data processing engine for extreme data scale

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Website

aws.amazon.com/dynamodb

www.exasol.com

geospock.com

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

www.exasol.com/resources

trafodion.apache.org/documentation.html

Developer

Amazon

Exasol

GeoSpock

Apache Software Foundation, originally developed by HP

Initial release

2012

2000

2014

Current release

2.0, September 2019

2.3.0, February 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

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

Java, Javascript

C++, Java

Server operating systems

hosted

Linux

Data scheme

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

yes

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

JDBC

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Lua
Python
R

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Hadoop integration

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per table

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.