DBMS > Alibaba Cloud AnalyticDB for PostgreSQL vs. Amazon Redshift vs. Google Cloud Datastore vs. Manticore Search

System Properties Comparison Alibaba Cloud AnalyticDB for PostgreSQL vs. Amazon Redshift vs. Google Cloud Datastore vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An online MPP (Massively Parallel Processing) data warehousing service based on Greenplum

Large scale data warehouse service for use with business intelligence tools

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

Multi-storage database for search, including full-text search.

Primary database model

Relational DBMS

Document store

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.68
Rank	#231	Overall
	#105	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

www.alibabacloud.com/product/hybriddb-postgresql

aws.amazon.com/redshift

cloud.google.com/datastore

manticoresearch.com

Technical documentation

www.alibabacloud.com/help/en/analyticdb-for-postgresql/latest/product-introduction-overview

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

manual.manticoresearch.com

Developer

Alibaba / Pivotal Software Inc. / PostgreSQL Global Development Group

Amazon (based on PostgreSQL)

Google

Manticore Software

Initial release

2016

2012

2008

2017

Current release

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

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

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Data scheme

yes

schema-free

Fixed schema

Typing

predefined data types such as float or date

yes

yes, details here

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

Secondary indexes

yes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

C
Java
Perl
Python
R

All languages supporting JDBC/ODBC

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

in Python

using Google App Engine

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication using Paxos

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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 based on Google Cloud Identity and Access Management (IAM)

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.