DBMS > Amazon Redshift vs. BigObject vs. Brytlyt vs. LMDB vs. Oracle Berkeley DB

System Properties Comparison Amazon Redshift vs. BigObject vs. Brytlyt vs. LMDB vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

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

A high performant, light-weight, embedded key-value database library

Widely used in-process key-value store

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	1.99
Rank	#125	Overall
	#21	Key-value stores

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/redshift

bigobject.io

brytlyt.io

www.symas.com/symas-embedded-database-lmdb

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

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

docs.brytlyt.io

www.lmdb.tech/doc

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

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Brytlyt

Symas

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2015

2016

2011

1994

Current release

5.0, August 2023

0.9.32, January 2024

18.1.40, May 2020

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

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

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

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
OS X
Windows

Linux
Unix
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
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.

yes

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

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

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
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

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

none

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

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.