DBMS > Amazon Redshift vs. Riak TS vs. SpatiaLite vs. TDSQL for MySQL vs. YDB

System Properties Comparison Amazon Redshift vs. Riak TS vs. SpatiaLite vs. TDSQL for MySQL vs. YDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Spatial extension of SQLite

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store
Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	0.85
Rank	#207	Overall
	#97	Relational DBMS

Score	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

aws.amazon.com/redshift

www.gaia-gis.it/fossil/libspatialite/index

www.tencentcloud.com/products/dcdb

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.aws.amazon.com/redshift

www.tiot.jp/riak-docs/riak/ts/latest

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.tencentcloud.com/document/product/1042

ydb.tech/en/docs

Developer

Amazon (based on PostgreSQL)

Open Source, formerly Basho Technologies

Alessandro Furieri

Tencent

Yandex

Initial release

2012

2015

2008

2013

2019

Current release

3.0.0, September 2022

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

Open Source

Apache 2.0; commercial license available

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

Erlang

C++

Server operating systems

hosted

Linux
OS X

server-less

hosted

Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, 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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, limited

yes

SQL-like query language (YQL)

APIs and other access methods

JDBC
ODBC

HTTP API
Native Erlang Interface

JDBC
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

All languages supporting JDBC/ODBC

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C#
C++
Java
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

Multi-source replication
Source-replica replication

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between datasets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

Access rights defined for Yandex Cloud users

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.