DBMS > Amazon Redshift vs. etcd vs. Oracle NoSQL vs. Tkrzw

System Properties Comparison Amazon Redshift vs. etcd vs. Oracle NoSQL 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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Relational DBMS

Key-value store

Document store
Key-value store
Relational DBMS

Key-value store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	3.07
Rank	#86	Overall
	#15	Document stores
	#11	Key-value stores
	#47	Relational DBMS

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

Website

aws.amazon.com/redshift

etcd.io
github.com/etcd-io/etcd

www.oracle.com/database/nosql/technologies/nosql

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Amazon (based on PostgreSQL)

Oracle

Mikio Hirabayashi

Initial release

2012

2011

2020

Current release

3.4, August 2019

24.1, May 2024

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

C++

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

Linux
Solaris SPARC/x86

Linux
macOS

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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 DML and DDL statements

APIs and other access methods

JDBC
ODBC

gRPC
JSON over HTTP

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C#
Go
Java
JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for 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.