DBMS > Brytlyt vs. Firebase Realtime Database vs. GeoSpock vs. InterSystems IRIS vs. Redis

System Properties Comparison Brytlyt vs. Firebase Realtime Database vs. GeoSpock vs. InterSystems IRIS vs. Redis

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Spatial and temporal data processing engine for extreme data scale

A containerised multi-model DBMS, interoperability and analytics data platform with wide capabilities for vertical and horizontal scalability

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.

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

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

Secondary database models

Time Series DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.05
Rank	#83	Overall
	#14	Document stores
	#10	Key-value stores
	#1	Object oriented DBMS
	#45	Relational DBMS

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

Website

brytlyt.io

firebase.google.com/products/realtime-database

geospock.com

www.intersystems.com/products/intersystems-iris

redis.com
redis.io

Technical documentation

docs.brytlyt.io

firebase.google.com/docs/database

docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls

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

Developer

Brytlyt

Google

acquired by Google 2014

GeoSpock

InterSystems

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2016

2012

2018

2009

Current release

5.0, August 2023

2.0, September 2019

2023.3, June 2023

7.2.5, May 2024

License

Commercial or Open Source

commercial

Open Source

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

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.

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

Implementation language

C, C++ and CUDA

Java, Javascript

Server operating systems

Linux
OS X
Windows

hosted

AIX
Linux
macOS
Ubuntu
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

yes

depending on used data model

schema-free

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

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

temporal, categorical

yes

with RediSearch module

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

with RediSQL module

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Android
iOS
JavaScript API
RESTful HTTP API

JDBC

JDBC
ODBC
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Java
JavaScript
Objective-C

.Net
C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

limited functionality with using 'rules'

yes

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

Triggers

yes

Callbacks are triggered when data changes

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Access rights for users can be defined per table

yes

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

More information provided by the system vendor

Specific characteristics

InterSystems IRIS is a complete cloud-first data platform which includes a multi-model...
» more

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.