DBMS > Amazon DynamoDB vs. Sphinx vs. Splice Machine vs. Tarantool vs. Transbase

System Properties Comparison Amazon DynamoDB vs. Sphinx vs. Splice Machine vs. Tarantool vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Search engine

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/dynamodb

sphinxsearch.com

splicemachine.com

www.tarantool.io

www.transaction.de/en/products/transbase.html

Technical documentation

docs.aws.amazon.com/dynamodb

sphinxsearch.com/docs

splicemachine.com/how-it-works

www.tarantool.io/en/doc

www.transaction.de/en/products/transbase/features.html

Developer

Amazon

Sphinx Technologies Inc.

Splice Machine

Transaction Software GmbH

Initial release

2012

2001

2014

2008

1987

Current release

3.5.1, February 2023

3.1, March 2021

2.10.0, May 2022

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

free development license

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

C and C++

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

BSD
Linux
macOS

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

yes

APIs and other access methods

RESTful HTTP API

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

Open binary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

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

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Lua, C and SQL stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

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

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

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 Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.