DBMS > Alibaba Cloud AnalyticDB for PostgreSQL vs. Google Cloud Datastore vs. Graphite vs. RocksDB vs. Tigris

System Properties Comparison Alibaba Cloud AnalyticDB for PostgreSQL vs. Google Cloud Datastore vs. Graphite vs. RocksDB vs. Tigris

Editorial information provided by DB-Engines

Name

Description

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

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Document store
Key-value store
Search engine
Time Series DBMS

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

Score	0.68
Rank	#231	Overall
	#105	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

www.alibabacloud.com/product/hybriddb-postgresql

cloud.google.com/datastore

github.com/graphite-project/graphite-web

rocksdb.org

www.tigrisdata.com

Technical documentation

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

cloud.google.com/datastore/docs

graphite.readthedocs.io

github.com/facebook/rocksdb/wiki

www.tigrisdata.com/docs

Developer

Alibaba / Pivotal Software Inc. / PostgreSQL Global Development Group

Google

Chris Davis

Facebook, Inc.

Tigris Data, Inc.

Initial release

2016

2008

2006

2013

2022

Current release

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2.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

Python

C++

Server operating systems

hosted

Linux
Unix

Linux

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

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

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC

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

HTTP API
Sockets

C++ API
Java API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C
Java
Perl
Python
R

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

JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

using Google App Engine

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

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication using Paxos

none

yes

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.

none

Immediate Consistency

Foreign keys

Referential integrity

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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)

Access rights for users and roles

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.