DBMS > Amazon Redshift vs. Brytlyt vs. GeoMesa vs. LMDB

System Properties Comparison Amazon Redshift vs. Brytlyt vs. GeoMesa vs. LMDB

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.94
Rank	#120	Overall
	#20	Key-value stores

Website

aws.amazon.com/redshift

brytlyt.io

www.geomesa.org

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

Technical documentation

docs.aws.amazon.com/redshift

docs.brytlyt.io

www.geomesa.org/documentation/stable/user/index.html

www.lmdb.tech/doc

Developer

Amazon (based on PostgreSQL)

Brytlyt

CCRi and others

Symas

Initial release

2012

2016

2014

2011

Current release

5.0, August 2023

5.0.1, July 2024

0.9.32, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

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

Scala

Server operating systems

hosted

Linux
OS X
Windows

Linux
Unix
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

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

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

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

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

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

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.