DBMS > Amazon Redshift vs. Faircom EDGE vs. Graph Engine vs. OpenTSDB

System Properties Comparison Amazon Redshift vs. Faircom EDGE vs. Graph Engine vs. OpenTSDB

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

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

Scalable Time Series DBMS based on HBase

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

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

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Website

aws.amazon.com/redshift

www.faircom.com/products/faircom-edge

www.graphengine.io

opentsdb.net

Technical documentation

docs.aws.amazon.com/redshift

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

www.graphengine.io/docs/manual

opentsdb.net/docs/build/html/index.html

Developer

Amazon (based on PostgreSQL)

FairCom Corporation

Microsoft

currently maintained by Yahoo and other contributors

Initial release

2012

1979

2010

2011

Current release

V3, October 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

MIT License

Open Source

LGPL

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

.NET and C

Java

Server operating systems

hosted

Android
Linux

ARM, x86
Raspbian
Windows

.NET

Linux
Windows

Data scheme

yes

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

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

yes

numeric data for metrics, strings for tags

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

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

RESTful HTTP API

HTTP API
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
F#
Visual Basic

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Immediate Consistency

based on HBase

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

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.

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.