DBMS > Faircom EDGE vs. Firebird vs. Memcached vs. QuestDB vs. Redis

System Properties Comparison Faircom EDGE vs. Firebird vs. Memcached vs. QuestDB vs. Redis

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

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

In-memory key-value store, originally intended for caching

A high performance open source SQL database for time series data

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

Key-value store
Relational DBMS

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

Secondary database models

Relational 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.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	2.70
Rank	#105	Overall
	#8	Time Series DBMS

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

Website

www.faircom.com/products/faircom-edge

Technical documentation

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

www.firebirdsql.org/en/reference-manuals

github.com/memcached/memcached/wiki

questdb.io/docs

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

Developer

FairCom Corporation

Firebird Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

QuestDB Technology Inc

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

1979

2000

As fork of Borland's InterBase

2003

2014

2009

Current release

V3, October 2020

5.0.0, January 2024

1.6.27, May 2024

7.2.5, May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Initial Developer's Public License

Open Source

BSD license

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.

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

Implementation language

ANSI C, C++

C and C++

Java (Zero-GC), C++, Rust

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

FreeBSD
Linux
OS X
Unix
Windows

Linux
macOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

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

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

schema-free

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

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

with RediSearch module

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL with time-series extensions

with RediSQL module

APIs and other access methods

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

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Proprietary protocol

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

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

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

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

PSQL

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

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

horizontal partitioning (by timestamps)

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication with eventual consistency

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
Tunable Consistency

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

when using SQL

yes

Transaction concepts

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

ACID

ACID for single-table writes

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

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

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

through memory mapped files

yes

User concepts

Access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Users with fine-grained authorization concept

yes

using SASL (Simple Authentication and Security Layer) protocol

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

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Fluid real-time dashboards with Grafana and QuestDB
11 June 2024

QuestDB 8.0: Major Release
23 May 2024

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 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.