DBMS > Alibaba Cloud AnalyticDB for PostgreSQL vs. Amazon DynamoDB vs. HBase vs. Sphinx vs. Tarantool

System Properties Comparison Alibaba Cloud AnalyticDB for PostgreSQL vs. Amazon DynamoDB vs. HBase vs. Sphinx vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Wide-column store based on Apache Hadoop and on concepts of BigTable

Open source search engine for searching in data from different sources, e.g. relational databases

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Document store
Key-value store

Wide column store

Search engine

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.76
Rank	#220	Overall
	#102	Relational DBMS

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

www.alibabacloud.com/product/hybriddb-postgresql

aws.amazon.com/dynamodb

hbase.apache.org

sphinxsearch.com

www.tarantool.io

Technical documentation

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

docs.aws.amazon.com/dynamodb

hbase.apache.org/book.html

sphinxsearch.com/docs

www.tarantool.io/en/doc

Developer

Alibaba / Pivotal Software Inc. / PostgreSQL Global Development Group

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Sphinx Technologies Inc.

Initial release

2016

2012

2008

2001

2008

Current release

2.3.4, January 2021

3.5.1, February 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2

Open Source

GPL version 2, commercial licence available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Java

C++

C and C++

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

schema-free

schema-free, schema definition possible

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

string, double, decimal, uuid, integer, blob, boolean, datetime

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

Java API
RESTful HTTP API
Thrift

Proprietary protocol

Open binary protocol

Supported programming languages

C
Java
Perl
Python
R

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Coprocessors in Java

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

yes

yes, before/after data modification events, on replication events, client session events

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

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

Single row ACID (across millions of columns)

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

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

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.