DBMS > Alibaba Cloud Table Store vs. Amazon Redshift vs. CouchDB vs. Google Cloud Firestore vs. PostGIS

System Properties Comparison Alibaba Cloud Table Store vs. Amazon Redshift vs. CouchDB vs. Google Cloud Firestore vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

Large scale data warehouse service for use with business intelligence tools

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/redshift

couchdb.apache.org

firebase.google.com/products/firestore

postgis.net

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

firebase.google.com/docs/firestore

postgis.net/documentation

Developer

Alibaba

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

Initial release

2016

2012

2005

2017

2005

Current release

3.3.3, December 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Erlang

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

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

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

HTTP API

JDBC
ODBC

RESTful HTTP/JSON API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

Java
Python

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

improved architecture with release 2.0

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

Multi-source replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Atomic single-row operations

ACID

atomic operations within a single document possible

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights based on subaccounts and tokens

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.