DBMS > Amazon Redshift vs. SQLite vs. TimescaleDB vs. Transbase vs. Yanza

System Properties Comparison Amazon Redshift vs. SQLite vs. TimescaleDB vs. Transbase vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Widely used embeddable, in-process RDBMS

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

A resource-optimized, high-performance, universally applicable RDBMS

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Relational DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

aws.amazon.com/redshift

www.sqlite.org

www.timescale.com

www.transaction.de/en/products/transbase.html

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

www.sqlite.org/docs.html

docs.timescale.com

www.transaction.de/en/products/transbase/features.html

Developer

Amazon (based on PostgreSQL)

Dwayne Richard Hipp

Timescale

Transaction Software GmbH

Yanza

Initial release

2012

2000

2017

1987

2015

Current release

3.46.1 (13 August 2024), August 2024

2.15.0, May 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

Apache 2.0

commercial

free development license

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Server operating systems

hosted

server-less

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Windows

Data scheme

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

yes

APIs and other access methods

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

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

yes

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication with hot standby and reads on replicas

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

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.