DBMS > Amazon Redshift vs. Brytlyt vs. EJDB vs. Graphite

System Properties Comparison Amazon Redshift vs. Brytlyt vs. EJDB vs. Graphite

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Primary database model

Relational DBMS

Document store

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	0.31
Rank	#296	Overall
	#44	Document stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/redshift

brytlyt.io

github.com/Softmotions/ejdb

github.com/graphite-project/graphite-web

Technical documentation

docs.aws.amazon.com/redshift

docs.brytlyt.io

github.com/Softmotions/ejdb/blob/master/README.md

graphite.readthedocs.io

Developer

Amazon (based on PostgreSQL)

Brytlyt

Softmotions

Chris Davis

Initial release

2012

2016

2012

2006

Current release

5.0, August 2023

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache 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

C, C++ and CUDA

Python

Server operating systems

hosted

Linux
OS X
Windows

server-less

Linux
Unix

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

Numeric data only

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

APIs and other access methods

JDBC
ODBC

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

in-process shared library

HTTP API
Sockets

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

in PL/pgSQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

locking

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

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.