DBMS > Amazon Redshift vs. Apache Phoenix vs. Faircom EDGE vs. Graph Engine

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Faircom EDGE vs. Graph Engine

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Graph DBMS
Key-value store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	2.02
Rank	#130	Overall
	#63	Relational DBMS

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

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Website

aws.amazon.com/redshift

phoenix.apache.org

www.faircom.com/products/faircom-edge

www.graphengine.io

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

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

www.graphengine.io/docs/manual

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

FairCom Corporation

Microsoft

Initial release

2012

2014

1979

2010

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

V3, October 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Restricted, free version available

Open Source

MIT License

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

Java

ANSI C, C++

.NET and C

Server operating systems

hosted

Linux
Unix
Windows

Android
Linux

ARM, x86
Raspbian
Windows

.NET

Data scheme

yes

late-bound, schema-on-read capabilities

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

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

ANSI SQL queries

APIs and other access methods

JDBC
ODBC

JDBC

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

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

Synchronous and asynchronous realtime replication based on transaction logs

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

when using SQL

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

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.