DBMS > Amazon Redshift vs. Databricks vs. Ingres vs. Riak KV

System Properties Comparison Amazon Redshift vs. Databricks vs. Ingres vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Well established RDBMS

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

aws.amazon.com/redshift

www.databricks.com

www.actian.com/databases/ingres

Technical documentation

docs.aws.amazon.com/redshift

docs.databricks.com

docs.actian.com/ingres

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Amazon (based on PostgreSQL)

Databricks

Actian Corporation

OpenSource, formerly Basho Technologies

Initial release

2012

2013

1974

originally developed at University Berkely in early 1970s

2009

Current release

11.2, May 2022

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
OS X

Data scheme

yes

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

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.

yes

but tools for importing/exporting data from/to XML-files available

Secondary indexes

restricted

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

Python
R
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

yes, using Riak Security

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.