DBMS > Amazon Redshift vs. EsgynDB vs. Faircom DB vs. OrientDB

System Properties Comparison Amazon Redshift vs. EsgynDB vs. Faircom DB vs. OrientDB

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

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Multi-model DBMS (Document, Graph, Key/Value)

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Website

aws.amazon.com/redshift

www.esgyn.cn

www.faircom.com/products/faircom-db

orientdb.org

Technical documentation

docs.aws.amazon.com/redshift

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.orientdb.com/docs/last/index.html

Developer

Amazon (based on PostgreSQL)

Esgyn

FairCom Corporation

OrientDB LTD; CallidusCloud; SAP

Initial release

2012

2015

1979

2010

Current release

V12, November 2020

3.2.29, March 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache version 2

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

C++, Java

ANSI C, C++

Java

Server operating systems

hosted

Linux

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

All OS with a Java JDK (>= JDK 6)

Data scheme

yes

schema free, schema optional, schema required, partial schema,

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

yes, ANSI SQL with proprietary extensions

SQL-like query language, no joins

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

.Net, JavaScript, C/C++

Java, Javascript

Triggers

yes

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationship in graphs

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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 access rights according to SQL-standard with additional protections for files

Access rights for users and roles; record level security configurable

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.