DBMS > Amazon Redshift vs. Brytlyt vs. Oracle Berkeley DB vs. Prometheus vs. SiteWhere

System Properties Comparison Amazon Redshift vs. Brytlyt vs. Oracle Berkeley DB vs. Prometheus vs. SiteWhere

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

Widely used in-process key-value store

Open-source Time Series DBMS and monitoring system

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

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	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

aws.amazon.com/redshift

brytlyt.io

www.oracle.com/database/technologies/related/berkeleydb.html

prometheus.io

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

docs.brytlyt.io

docs.oracle.com/cd/E17076_05/html/index.html

prometheus.io/docs

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Brytlyt

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SiteWhere

Initial release

2012

2016

1994

2015

2010

Current release

5.0, August 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.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

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

hosted

Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

yes

Numeric data only

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.

yes

only with the Berkeley DB XML edition

Import of XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP/JSON API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

in PL/pgSQL

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

by Federation

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

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

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

Users with fine-grained authorization concept

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.