DBMS > Firebird vs. Hazelcast vs. Redis vs. Sqrrl vs. Titan

System Properties Comparison Firebird vs. Hazelcast vs. Redis vs. Sqrrl vs. Titan

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Firebird is an open source RDBMS forked from Borland's InterBase

A widely adopted in-memory data grid

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.

Adaptable, secure NoSQL built on Apache Accumulo

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Key-value store

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

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Website

www.firebirdsql.org

hazelcast.com

redis.com
redis.io

sqrrl.com

github.com/thinkaurelius/titan

Technical documentation

www.firebirdsql.org/en/reference-manuals

hazelcast.org/imdg/docs

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

github.com/thinkaurelius/titan/wiki

Developer

Firebird Foundation

Hazelcast

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Amazon

originally Sqrrl Data, Inc.

Aurelius, owned by DataStax

Initial release

2000

As fork of Borland's InterBase

2008

2009

2012

Current release

5.0.0, January 2024

5.3.6, November 2023

7.2.4, January 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

Apache Version 2; commercial licenses available

Open Source

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

commercial

Open Source

Apache license, 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.

Implementation language

C and C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

All OS with a Java VM

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Linux
OS X
Unix
Windows

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

the object must implement a serialization strategy

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

yes

SQL-like query language

with RediSQL module

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JCache
JPA
Memcached protocol
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Clojure
Java
Python

Server-side scripts

Stored procedures

PSQL

yes

Event Listeners, Executor Services

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

yes

Triggers

yes

Events

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

making use of Hadoop

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

selectable replication factor

making use of Hadoop

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

Atomic execution of command blocks and scripts and optimistic locking

Atomic updates per row, document, or graph entity

ACID

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

Role-based 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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

User authentification and security via Rexster Graph Server

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.