DBMS > Bangdb vs. Faircom DB vs. ObjectBox vs. Prometheus vs. Redis

System Properties Comparison Bangdb vs. Faircom DB vs. ObjectBox vs. Prometheus vs. Redis

Editorial information provided by DB-Engines

Name

Description

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

Open-source Time Series DBMS and monitoring system

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
Relational DBMS

Object oriented DBMS
Vector DBMS

Time Series 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

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.07
Rank	#346	Overall
	#47	Document stores
	#35	Graph DBMS
	#32	Time Series DBMS

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	1.08
Rank	#179	Overall
	#6	Object oriented DBMS
	#9	Vector DBMS

Score	7.56
Rank	#49	Overall
	#3	Time Series DBMS

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

Website

bangdb.com

www.faircom.com/products/faircom-db

github.com/objectbox
objectbox.io

prometheus.io

redis.com
redis.io

Technical documentation

docs.bangdb.com

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.objectbox.io

prometheus.io/docs

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

Developer

Sachin Sinha, BangDB

FairCom Corporation

ObjectBox Limited

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

1979

2017

2015

2009

Current release

BangDB 2.0, October 2021

V13, July 2024

4.0 (May 2024)

7.2.5, May 2024

License

Commercial or Open Source

Open Source

BSD 3

commercial

Restricted, free version available

Bindings are released under Apache 2.0

Apache License 2.0

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

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++

ANSI C, C++

C and C++

Server operating systems

Linux

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

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

yes, ANSI SQL Types, JSON, typed binary structures

yes, plus "flex" map-like types

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

with RediSearch module

SQL

Support of SQL

SQL like support with command line tool

yes, ANSI SQL with proprietary extensions

with RediSQL module

APIs and other access methods

Proprietary protocol
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Proprietary native API

RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C
C#
C++
Java
Python

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

yes

.Net, JavaScript, C/C++

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

Triggers

yes, Notifications (with Streaming only)

yes

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

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

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)

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Data sync between devices allowing occasional connected databases to work completely offline

yes

by Federation

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

Tunable consistency, set CAP knob accordingly

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

none

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

tunable from ACID to Eventually Consistent

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, tunable from durable to delayed durability to in-memory

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)

Fine grained access rights according to SQL-standard with additional protections for files

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

News

MongoDB Realm & Device Sync alternatives – ObjectBox
17 September 2024

Local AI – what it is and why we need it
11 September 2024

First on-device Vector Database (aka Semantic Index) for iOS
24 July 2024

Retrieval Augmented Generation (RAG) with vector databases: Expanding AI Capabilities
18 June 2024

The on-device Vector Database for Android and Java
29 May 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.