DBMS > Amazon Redshift vs. SWC-DB vs. Transbase vs. Vitess vs. WakandaDB

System Properties Comparison Amazon Redshift vs. SWC-DB vs. Transbase vs. Vitess vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A high performance, scalable Wide Column DBMS

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

Scalable, distributed, cloud-native DBMS, extending MySQL

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Time Series 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.08
Rank	#364	Overall
	#13	Wide column stores

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

github.com/kashirin-alex/swc-db
www.swcdb.org

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

vitess.io

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

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

vitess.io/docs

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

Alex Kashirin

Transaction Software GmbH

The Linux Foundation, PlanetScale

Wakanda SAS

Initial release

2012

2020

1987

2013

2012

Current release

0.5, April 2021

Transbase 8.3, 2022

15.0.2, December 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3

commercial

free development license

Open Source

Apache Version 2.0, commercial licenses available

Open Source

AGPLv3, extended 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

C++

C and C++

C++, JavaScript

Server operating systems

hosted

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Docker
Linux
macOS

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C++

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

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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 across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

no user groups or roles

yes

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.