DBMS > Faircom DB vs. Faircom EDGE vs. Greenplum vs. H2 vs. Redis

System Properties Comparison Faircom DB vs. Faircom EDGE vs. Greenplum vs. H2 vs. Redis

Editorial information provided by DB-Engines

Name

Description

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

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

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

Document store
Spatial DBMS

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.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

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

Website

www.faircom.com/products/faircom-db

www.faircom.com/products/faircom-edge

greenplum.org

www.h2database.com

redis.com
redis.io

Technical documentation

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

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

docs.greenplum.org

www.h2database.com/html/main.html

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

Developer

FairCom Corporation

Pivotal Software Inc.

Thomas Mueller

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

1979

2005

2009

Current release

V12, November 2020

V3, October 2020

7.0.0, September 2023

2.2.220, July 2023

7.2.4, January 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Restricted, free version available

Open Source

Apache 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

Java

Server operating systems

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

easily portable to other OSs

Android
Linux

ARM, x86
Raspbian
Windows

Linux

All OS with a Java VM

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

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

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

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

since Version 4.2

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

ANSI SQL queries

yes

with RediSQL module

APIs and other access methods

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

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

JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

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

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

C
Java
Perl
Python
R

Java

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

yes

.Net, JavaScript, C/C++

yes

Java Stored Procedures and User-Defined Functions

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, horizontal partitioning, sharding

Customizable business rules for table partitioning

File partitioning

Customizable business rules for partitioning

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

With clustering: 2 database servers on different computers operate on identical copies of a database

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

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

across SQL and NoSQL

yes

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

Durability

Support for making data persistent

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

User concepts

Access control

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

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

fine grained access rights according to SQL-standard

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.