DBMS > Amazon Redshift vs. Brytlyt vs. Infobright vs. RavenDB

System Properties Comparison Amazon Redshift vs. Brytlyt vs. Infobright vs. RavenDB

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series 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	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

brytlyt.io

ignitetech.com/softwarelibrary/infobrightdb

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

docs.brytlyt.io

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Brytlyt

Ignite Technologies Inc.; formerly InfoBright Inc.

Hibernating Rhinos

Initial release

2012

2016

2005

2010

Current release

5.0, August 2023

5.4, July 2022

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

AGPL version 3, 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 CUDA

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

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

ADO.NET
JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

in PL/pgSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Authorization levels configured per client per database

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.