DBMS > Faircom EDGE vs. Ingres vs. Oracle NoSQL vs. Redis vs. Vertica

System Properties Comparison Faircom EDGE vs. Ingres vs. Oracle NoSQL vs. Redis vs. Vertica

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

Well established RDBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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.

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Key-value store

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

Relational DBMS

Column oriented

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

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

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

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

Score	10.68
Rank	#43	Overall
	#27	Relational DBMS

Website

www.faircom.com/products/faircom-edge

www.actian.com/databases/ingres

www.oracle.com/database/nosql/technologies/nosql

redis.com
redis.io

www.vertica.com

Technical documentation

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

docs.actian.com/ingres

docs.oracle.com/en/database/other-databases/nosql-database/index.html

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

vertica.com/documentation

Developer

FairCom Corporation

Actian Corporation

Oracle

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

OpenText

previously Micro Focus and Hewlett Packard

Initial release

1979

1974

originally developed at University Berkely in early 1970s

2011

2009

2005

Current release

V3, October 2020

11.2, May 2022

23.3, December 2023

7.2.4, January 2024

12.0.3, January 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

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

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

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

C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
Solaris SPARC/x86

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

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

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

optional

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

with RediSearch module

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL-like DML and DDL statements

with RediSQL module

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

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

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

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

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

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

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Ingres Replicator

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

through RedisGears

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

MVCC

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

off heap cache

yes

User concepts

Access control

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 rights for users and roles

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

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.