DBMS > Amazon Redshift vs. Faircom EDGE vs. mSQL vs. OrigoDB vs. ToroDB

System Properties Comparison Amazon Redshift vs. Faircom EDGE vs. mSQL vs. OrigoDB vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines 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

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store
Object oriented DBMS

Document store

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	1.27
Rank	#167	Overall
	#77	Relational DBMS

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

Website

aws.amazon.com/redshift

www.faircom.com/products/faircom-edge

hughestech.com.au/products/msql

origodb.com

github.com/torodb/server

Technical documentation

docs.aws.amazon.com/redshift

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

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

FairCom Corporation

Hughes Technologies

Robert Friberg et al

8Kdata

Initial release

2012

1979

1994

2009

under the name LiveDB

2016

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

Open Source

AGPL-V3

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

Java

Server operating systems

hosted

Android
Linux

ARM, x86
Raspbian
Windows

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

Linux
Windows

All OS with a Java 7 VM

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

User defined using .NET types and collections

yes

string, integer, double, boolean, date, object_id

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

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

ANSI SQL queries

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

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

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

Sharding

File partitioning

Customizable business rules for partitioning

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

Source-replica replication

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

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

when using SQL

depending on model

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

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

fine grained access rights according to SQL-standard

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

Role based authorization

Access rights for users and roles

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.