DBMS > Redis vs. Tarantool vs. Trino

System Properties Comparison Redis vs. Tarantool vs. Trino

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

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

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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	156.44
Rank	#6	Overall
	#1	Key-value stores

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Score	5.10
Rank	#70	Overall
	#38	Relational DBMS

Website

redis.com
redis.io

www.tarantool.io

trino.io

Technical documentation

docs.redis.com/latest/index.html
redis.io/docs

www.tarantool.io/en/doc

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

Social network pages

Developer

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Trino Software Foundation

Initial release

2009

2008

2012

2020 rebranded from PrestoSQL

Current release

7.2.4, January 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

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

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

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

Implementation language

C and C++

Java

Server operating systems

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

BSD
Linux
macOS

Linux
macOS

for devlopment

Data scheme

schema-free

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

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

with RediSearch module

yes

depending on connected data-source

SQL

Support of SQL

with RediSQL module

Full-featured ANSI SQL support

yes

APIs and other access methods

proprietary protocol

RESP - REdis Serialization Protocol

Open binary protocol

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Lua; Redis Functions coming in Redis 7 (slides and Github)

Lua, C and SQL stored procedures

yes, depending on connected data-source

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

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

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

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

Atomic execution of command blocks and scripts and optimistic locking

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

Data access is serialized by the server

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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 Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

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

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

58: Understanding your users with Trino and Mitzu
4 April 2024

57: Seeing clearly with OpenTelemetry
14 March 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.