DBMS > EsgynDB vs. Faircom EDGE vs. Greenplum vs. Redis vs. SpatiaLite

System Properties Comparison EsgynDB vs. Faircom EDGE vs. Greenplum vs. Redis vs. SpatiaLite

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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.

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.

Spatial extension of SQLite

Primary database model

Relational DBMS

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

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Relational DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

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

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

www.esgyn.cn

www.faircom.com/products/faircom-edge

greenplum.org

redis.com
redis.io

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

docs.greenplum.org

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

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Esgyn

FairCom Corporation

Pivotal Software Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Alessandro Furieri

Initial release

2015

1979

2005

2009

2008

Current release

V3, October 2020

7.0.0, September 2023

7.2.5, May 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache 2.0

Open Source

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

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++, Java

ANSI C, C++

C++

Server operating systems

Linux

Android
Linux

ARM, x86
Raspbian
Windows

Linux

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

server-less

Data scheme

yes

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

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

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

with RediSQL module

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

All languages supporting JDBC/ODBC/ADO.Net

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

C
Java
Perl
Python
R

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

Java Stored Procedures

yes

.Net, JavaScript, C/C++

yes

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

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Atomic execution of command blocks and scripts and optimistic locking

ACID

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 access rights according to SQL-standard

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.