DBMS > Amazon Redshift vs. Dolt vs. Infobright vs. MaxDB vs. SwayDB

System Properties Comparison Amazon Redshift vs. Dolt vs. Infobright vs. MaxDB vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A MySQL compatible DBMS with Git-like versioning of data and schema

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A robust and reliable RDBMS optimized to run all major SAP solutions

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

aws.amazon.com/redshift

github.com/dolthub/dolt
www.dolthub.com

ignitetech.com/softwarelibrary/infobrightdb

maxdb.sap.com

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/redshift

docs.dolthub.com

maxdb.sap.com/documentation

Developer

Amazon (based on PostgreSQL)

DoltHub Inc

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP, acquired from Software AG (Adabas-D) in 1997

Simer Plaha

Initial release

2012

2018

2005

1984

2018

Current release

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Limited community edition free

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

hosted

Linux
macOS
Windows

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

All languages supporting JDBC/ODBC

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
Perl
PHP
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

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.