DBMS > Amazon Neptune vs. Amazon Redshift vs. Faircom DB vs. OrigoDB vs. Rockset

System Properties Comparison Amazon Neptune vs. Amazon Redshift vs. Faircom DB vs. OrigoDB vs. Rockset

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Large scale data warehouse service for use with business intelligence tools

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

A fully ACID in-memory object graph database

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Graph DBMS
RDF store

Relational DBMS

Key-value store
Relational DBMS

Document store
Object oriented DBMS

Document store

Secondary database models

Relational DBMS
Search engine

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

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

aws.amazon.com/neptune

aws.amazon.com/redshift

www.faircom.com/products/faircom-db

origodb.com

rockset.com

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

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

origodb.com/docs

docs.rockset.com

Developer

Amazon

Amazon (based on PostgreSQL)

FairCom Corporation

Robert Friberg et al

Rockset

Initial release

2017

2012

1979

2009

under the name LiveDB

2019

Current release

V12, November 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

commercial

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

C++

Server operating systems

hosted

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

easily portable to other OSs

Linux
Windows

hosted

Data scheme

schema-free

yes

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

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

User defined using .NET types and collections

dynamic typing

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.

can be achieved using .NET

ingestion from XML files supported

Secondary indexes

restricted

yes

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, ANSI SQL with proprietary extensions

Read-only SQL queries, including JOINs

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

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

.NET Client API
HTTP API
LINQ

HTTP REST

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

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

.Net

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

horizontal partitioning

client side managed; servers are not synchronized

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

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

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

informational only, not enforced by the system

yes

depending on model

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

with encyption-at-rest

yes

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

yes

Write ahead log

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Fine grained access rights according to SQL-standard with additional protections for files

Role based authorization

Access rights for users and organizations can be defined via Rockset console

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.