DBMS > Amazon Redshift vs. Databricks vs. PostGIS vs. WakandaDB

System Properties Comparison Amazon Redshift vs. Databricks vs. PostGIS vs. WakandaDB

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.

Spatial extension of PostgreSQL

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Document store
Relational DBMS

Spatial DBMS

Object oriented DBMS

Secondary database models

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

aws.amazon.com/redshift

www.databricks.com

postgis.net

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

docs.databricks.com

postgis.net/documentation

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

Databricks

Wakanda SAS

Initial release

2012

2013

2005

2012

Current release

3.4.2, February 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

AGPLv3, extended commercial license 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

C++, JavaScript

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

yes

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

yes

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

Secondary indexes

restricted

yes

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

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Python
R
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

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

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

yes

based on PostgreSQL

yes

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.