DBMS > Amazon Redshift vs. Faircom EDGE vs. FatDB vs. IBM Cloudant vs. mSQL

System Properties Comparison Amazon Redshift vs. Faircom EDGE vs. FatDB vs. IBM Cloudant vs. mSQL

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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 .NET NoSQL DBMS that can integrate with and extend SQL Server.

Database as a Service offering based on Apache CouchDB

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store
Key-value store

Document store

Relational 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	2.68
Rank	#106	Overall
	#20	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Website

aws.amazon.com/redshift

www.faircom.com/products/faircom-edge

www.ibm.com/products/cloudant

hughestech.com.au/products/msql

Technical documentation

docs.aws.amazon.com/redshift

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

cloud.ibm.com/docs/Cloudant

Developer

Amazon (based on PostgreSQL)

FairCom Corporation

FatCloud

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Hughes Technologies

Initial release

2012

1979

2012

2010

1994

Current release

V3, October 2020

4.4, October 2021

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

free licenses can be provided

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

Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

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

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

Via inetgration in SQL Server

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

yes

via applications

View functions (Map-Reduce) in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

Multi-source replication
Source-replica replication

none

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
Immediate Consistency

Eventual Consistency

none

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

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Optimistic locking

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.

Can implement custom security layer via applications

Access rights for users can be defined per database

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.