DBMS > Amazon DynamoDB vs. GeoMesa vs. Sphinx vs. Trafodion

System Properties Comparison Amazon DynamoDB vs. GeoMesa vs. Sphinx vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Open source search engine for searching in data from different sources, e.g. relational databases

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Spatial DBMS

Search engine

Relational DBMS

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

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/dynamodb

www.geomesa.org

sphinxsearch.com

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

www.geomesa.org/documentation/stable/user/index.html

sphinxsearch.com/docs

trafodion.apache.org/documentation.html

Developer

Amazon

CCRi and others

Sphinx Technologies Inc.

Apache Software Foundation, originally developed by HP

Initial release

2012

2014

2001

2014

Current release

4.0.5, February 2024

3.5.1, February 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache License 2.0

Open Source

GPL version 2, commercial licence available

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

Scala

C++

C++, Java

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

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

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (SphinxQL)

yes

APIs and other access methods

RESTful HTTP API

Proprietary protocol

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

depending on storage layer

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

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

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

depending on storage layer

User concepts

Access control

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

yes

depending on the DBMS used for storage

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.