DBMS > Amazon Redshift vs. Apache Kylin vs. EXASOL vs. Faircom DB vs. Machbase Neo

System Properties Comparison Amazon Redshift vs. Apache Kylin vs. EXASOL vs. Faircom DB vs. Machbase Neo

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

TimeSeries DBMS for AIoT and BigData

Primary database model

Relational DBMS

Key-value store
Relational DBMS

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	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Website

aws.amazon.com/redshift

kylin.apache.org

www.exasol.com

www.faircom.com/products/faircom-db

machbase.com

Technical documentation

docs.aws.amazon.com/redshift

kylin.apache.org/docs

www.exasol.com/resources

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

machbase.com/dbms

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation, originally contributed from eBay Inc

Exasol

FairCom Corporation

Machbase

Initial release

2012

2015

2000

1979

2013

Current release

3.1.0, July 2020

V12, November 2020

V8.0, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Restricted, free version available

commercial

free test version available

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

Java

ANSI C, C++

Server operating systems

hosted

Linux

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

easily portable to other OSs

Linux
macOS
Windows

Data scheme

yes

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

yes

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

ANSI SQL for queries (using Apache Calcite)

yes

yes, ANSI SQL with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

.Net, JavaScript, C/C++

Triggers

yes

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

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

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

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

simple password-based access control

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.