DBMS > Amazon Redshift vs. Badger vs. RisingWave vs. Tkrzw

System Properties Comparison Amazon Redshift vs. Badger vs. RisingWave vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.14
Rank	#328	Overall
	#48	Key-value stores

Score	0.61
Rank	#237	Overall
	#111	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

aws.amazon.com/redshift

github.com/dgraph-io/badger

www.risingwave.com/database

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

godoc.org/github.com/dgraph-io/badger

docs.risingwave.com/docs/current/intro

Developer

Amazon (based on PostgreSQL)

DGraph Labs

RisingWave Labs

Mikio Hirabayashi

Initial release

2012

2017

2022

2020

Current release

1.2, September 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 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

Rust

C++

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Standard SQL-types and JSON

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

APIs and other access methods

JDBC
ODBC

JDBC
PostgreSQL wire protocol

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

UDFs in Python or Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

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.