DBMS > Faircom EDGE vs. Firebase Realtime Database vs. Oracle Berkeley DB vs. Redis vs. Solr

System Properties Comparison Faircom EDGE vs. Firebase Realtime Database vs. Oracle Berkeley DB vs. Redis vs. Solr

Editorial information provided by DB-Engines

Name

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Widely used in-process key-value store

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.

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Key-value store
Relational DBMS

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

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

Search engine

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Spatial DBMS

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

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

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

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

www.faircom.com/products/faircom-edge

firebase.google.com/products/realtime-database

www.oracle.com/database/technologies/related/berkeleydb.html

redis.com
redis.io

solr.apache.org

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

firebase.google.com/docs/database

docs.oracle.com/cd/E17076_05/html/index.html

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

solr.apache.org/resources.html

Developer

FairCom Corporation

Google

acquired by Google 2014

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Apache Software Foundation

Initial release

1979

2012

1994

2009

2006

Current release

V3, October 2020

18.1.40, May 2020

7.2.5, May 2024

9.6.1, May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

commercial license available

Open Source

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

Open Source

Apache Version 2

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

ANSI C, C++

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

partial

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

yes

supports customizable data types and automatic typing

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

with RediSearch module

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL interfaced based on SQLite is available

with RediSQL module

Solr Parallel SQL Interface

APIs and other access methods

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

Java
JavaScript
Objective-C

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

limited functionality with using 'rules'

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

Java plugins

Triggers

yes

Callbacks are triggered when data changes

yes

only for the SQL API

publish/subscribe channels provide some trigger functionality; RedisGears

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

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 user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

yes, based on authentication and database rules

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

yes

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.