DBMS > Ignite vs. Redis vs. Trino

System Properties Comparison Ignite vs. Redis vs. Trino

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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.

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

Primary database model

Key-value store
Relational DBMS

Key-value store

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

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

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	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	5.00
Rank	#66	Overall
	#36	Relational DBMS

Website

ignite.apache.org

redis.com
redis.io

trino.io

Technical documentation

apacheignite.readme.io/docs

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

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

Social network pages

Developer

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Trino Software Foundation

Initial release

2015

2009

2012

2020 rebranded from PrestoSQL

Current release

Apache Ignite 2.6

7.2.4, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

source-available extensions (modules), commercial licenses for Redis 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++, Java, .Net

Java

Server operating systems

Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
macOS

for devlopment

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

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

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

with RediSearch module

depending on connected data-source

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

with RediSQL module

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

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

yes, depending on connected data-source

Triggers

yes (cache interceptors and events)

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

depending on connected data-source

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

depending on connected data-source

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Atomic execution of command blocks and scripts and optimistic locking

depending on connected data-source

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

User concepts

Access control

Security Hooks for custom implementations

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

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.