DBMS > Amazon DynamoDB vs. Graph Engine vs. Splice Machine vs. Tarantool vs. Trino

System Properties Comparison Amazon DynamoDB vs. Graph Engine vs. Splice Machine vs. Tarantool vs. Trino

Editorial information provided by DB-Engines

Name

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Fast distributed SQL query engine for big data analytics. Forked from Presto and originally named PrestoSQL

Primary database model

Document store
Key-value store

Graph DBMS
Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

Document store
Key-value store
Spatial DBMS
Search engine
Time Series DBMS
Wide column store

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.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	5.00
Rank	#66	Overall
	#36	Relational DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

www.graphengine.io/docs/manual

splicemachine.com/how-it-works

www.tarantool.io/en/doc

trino.io/broadcast
trino.io/docs/current

Social network pages

Developer

Amazon

Microsoft

Splice Machine

Trino Software Foundation

Initial release

2012

2010

2014

2008

2012

2020 rebranded from PrestoSQL

Current release

3.1, March 2021

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

Open Source

AGPL 3.0, commercial license available

Open Source

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

Open Source

Apache Version 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.

Starburst Galaxy offers a feature-rich user interface to connect all your data sources, manage your Trino clusters, and query your data.

Implementation language

.NET and C

Java

C and C++

Java

Server operating systems

hosted

.NET

Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Linux
macOS

for devlopment

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

depending on connected data-source

SQL

Support of SQL

yes

Full-featured ANSI SQL support

yes

APIs and other access methods

RESTful HTTP API

JDBC
Native Spark Datasource
ODBC

Open binary protocol

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

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

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

yes

Java

Lua, C and SQL stored procedures

yes, depending on connected data-source

Triggers

yes

by integration with AWS Lambda

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

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.

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

depending on connected data-source

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

depending on connected data-source

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

depending on connected data-source

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

yes, write ahead logging

depending on connected data-source

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

SQL standard access control

More information provided by the system vendor

Specific characteristics

Trino is the fastest open source, massively parallel processing SQL query engine...
» more

Competitive advantages

High performance analtyics and data processing of very large data sets Powerful ANSI...
» more

Typical application scenarios

Performant analytics query engine for data warehouses, data lakes, and data lakehouses...
» more

Key customers

Trino is widely adopted across the globe as freely-available open source software....
» more

Market metrics

33000+ commits in GitHub 8200+ stargazers in GitHub 1200+ pull requests merged in...
» more

Licensing and pricing models

Trino is an open source project and usage is therefore free. Commercial offerings...
» more

News

60: Trino calling AI
22 May 2024

Big names round out the Trino Fest 2024 lineup
8 May 2024

59: Querying Trino with Java and jOOQ
24 April 2024

A sneak peek of Trino Fest 2024
15 April 2024

Time travel in Delta Lake connector
11 April 2024

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.