DBMS > Amazon Redshift vs. BigObject vs. EXASOL vs. Google Cloud Datastore vs. PostGIS

System Properties Comparison Amazon Redshift vs. BigObject vs. EXASOL vs. Google Cloud Datastore vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Document store

Spatial 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	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

aws.amazon.com/redshift

bigobject.io

www.exasol.com

cloud.google.com/datastore

postgis.net

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

www.exasol.com/resources

cloud.google.com/datastore/docs

postgis.net/documentation

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Exasol

Google

Initial release

2012

2015

2000

2008

2005

Current release

3.4.2, February 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

GPL v2.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

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like DML and DDL statements

yes

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

user defined functions

using Google App Engine

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication using Paxos

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

based on PostgreSQL

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.