DBMS > Alibaba Cloud AnalyticDB for PostgreSQL vs. Heroic vs. MySQL vs. TinkerGraph

System Properties Comparison Alibaba Cloud AnalyticDB for PostgreSQL vs. Heroic vs. MySQL vs. TinkerGraph

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used open source RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.76
Rank	#220	Overall
	#102	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

www.alibabacloud.com/product/hybriddb-postgresql

github.com/spotify/heroic

www.mysql.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

spotify.github.io/heroic

dev.mysql.com/doc

Developer

Alibaba / Pivotal Software Inc. / PostgreSQL Global Development Group

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2014

1995

2009

Current release

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Java

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

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

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

TinkerPop 3

Supported programming languages

C
Java
Perl
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Groovy
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

optional

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

Users with fine-grained authorization concept

no user groups or 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.