DBMS > Bangdb vs. Cachelot.io vs. Firebase Realtime Database vs. Ignite vs. Redis

System Properties Comparison Bangdb vs. Cachelot.io vs. Firebase Realtime Database vs. Ignite vs. Redis

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

In-memory caching system

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

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.

Primary database model

Document store
Graph DBMS
Time Series DBMS

Key-value store

Document store

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

Secondary database models

Spatial 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.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Website

bangdb.com

cachelot.io

firebase.google.com/products/realtime-database

ignite.apache.org

redis.com
redis.io

Technical documentation

docs.bangdb.com

firebase.google.com/docs/database

apacheignite.readme.io/docs

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

Developer

Sachin Sinha, BangDB

Google

acquired by Google 2014

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2015

2012

2015

2009

Current release

BangDB 2.0, October 2021

Apache Ignite 2.6

7.2.4, January 2024

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Simplified BSD License

commercial

Open Source

Apache 2.0

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++

C++

C++, Java, .Net

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

with RediSearch module

SQL

Support of SQL

SQL like support with command line tool

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

with RediSQL module

APIs and other access methods

Proprietary protocol
RESTful HTTP API

Memcached protocol

Android
iOS
JavaScript API
RESTful HTTP API

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

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C
C#
C++
Java
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Java
JavaScript
Objective-C

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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

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

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

Triggers

yes, Notifications (with Streaming only)

Callbacks are triggered when data changes

yes (cache interceptors and events)

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

none

yes (replicated cache)

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

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

Tunable consistency, set CAP knob accordingly

none

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

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, optimistic concurrency control

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

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, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

yes, based on authentication and database rules

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

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.