DBMS > Amazon DynamoDB vs. GeoMesa vs. Solr vs. Sphinx vs. Splice Machine

System Properties Comparison Amazon DynamoDB vs. GeoMesa vs. Solr vs. Sphinx vs. Splice Machine

Editorial information provided by DB-Engines

Name

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.

A widely used distributed, scalable search engine based on Apache Lucene

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Document store
Key-value store

Spatial DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

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

solr.apache.org/resources.html

sphinxsearch.com/docs

splicemachine.com/how-it-works

Developer

Amazon

CCRi and others

Apache Software Foundation

Sphinx Technologies Inc.

Splice Machine

Initial release

2012

2014

2006

2001

2014

Current release

5.0.0, May 2024

9.6.1, May 2024

3.5.1, February 2023

3.1, March 2021

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache License 2.0

Open Source

Apache Version 2

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license available

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

Java

C++

Java

Server operating systems

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

yes

All search fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

Solr Parallel SQL Interface

SQL-like query language (SphinxQL)

yes

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP/JSON API

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

Java plugins

yes

Java

Triggers

yes

by integration with AWS Lambda

yes

User configurable commands triggered on index changes

yes

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

depending on storage layer

Eventual Consistency

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

yes

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

yes

Access rights for users, groups and roles 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.