DBMS > Alibaba Cloud Table Store vs. Amazon Redshift vs. Hazelcast vs. RDF4J vs. TimescaleDB

System Properties Comparison Alibaba Cloud Table Store vs. Amazon Redshift vs. Hazelcast vs. RDF4J vs. TimescaleDB

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 widely adopted in-memory data grid

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Relational DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/redshift

hazelcast.com

rdf4j.org

www.timescale.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

rdf4j.org/documentation

docs.timescale.com

Developer

Alibaba

Amazon (based on PostgreSQL)

Hazelcast

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Timescale

Initial release

2016

2012

2008

2004

2017

Current release

5.3.6, November 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Eclipse Distribution License (EDL), v1.0.

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.

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

the object must implement a serialization strategy

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java
Python

All languages supporting JDBC/ODBC

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Replicated Map

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

Role-based access control

fine grained access rights according to SQL-standard

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.