DBMS > Amazon Redshift vs. Faircom EDGE vs. Riak KV

System Properties Comparison Amazon Redshift vs. Faircom EDGE vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.03
Rank	#380	Overall
	#59	Key-value stores
	#157	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

aws.amazon.com/redshift

www.faircom.com/products/faircom-edge

Technical documentation

docs.aws.amazon.com/redshift

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Amazon (based on PostgreSQL)

FairCom Corporation

OpenSource, formerly Basho Technologies

Initial release

2012

1979

2009

Current release

V3, October 2020

3.2.0, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache version 2, commercial enterprise edition

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.

Implementation language

ANSI C, C++

Erlang

Server operating systems

hosted

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

restricted

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

ANSI SQL queries

APIs and other access methods

JDBC
ODBC

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

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

when using SQL

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

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.

yes, using Riak Security

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.