DBMS > Amazon Redshift vs. Brytlyt vs. TerminusDB vs. VoltDB

System Properties Comparison Amazon Redshift vs. Brytlyt vs. TerminusDB vs. VoltDB

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

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
RDF store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

brytlyt.io

terminusdb.com

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.brytlyt.io

terminusdb.github.io/terminusdb/#

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Brytlyt

DataChemist Ltd.

VoltDB Inc.

Initial release

2012

2016

2018

2010

Current release

5.0, August 2023

11.0.0, January 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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 CUDA

Prolog, Rust

Java, C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

Linux
OS X

for development

Data scheme

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.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (WOQL)

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

JavaScript
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

in PL/pgSQL

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Journaling Streams

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory journaling

yes

Snapshots and command logging

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

Role-based access control

Users and roles with access to stored procedures

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.