DBMS > Amazon Redshift vs. Brytlyt vs. GridDB vs. Rockset vs. Vitess

System Properties Comparison Amazon Redshift vs. Brytlyt vs. GridDB vs. Rockset vs. Vitess

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 in-memory time series database optimized for IoT and Big Data

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Key-value store
Relational DBMS

Relational DBMS
Search engine

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.38
Rank	#276	Overall
	#127	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

Developer

Amazon (based on PostgreSQL)

Brytlyt

Toshiba Corporation

Rockset

The Linux Foundation, PlanetScale

Initial release

2012

2016

2013

2019

2013

Current release

5.0, August 2023

5.1, August 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

Apache Version 2.0, commercial licenses 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 CUDA

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

hosted

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

restricted

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92, SQL-like TQL (Toshiba Query Language)

Read-only SQL queries, including JOINs

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

in PL/pgSQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

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

ACID at container level

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users can be defined per database

Access rights for users and organizations can be defined via Rockset console

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.