DBMS > Amazon DynamoDB vs. Brytlyt vs. GeoMesa vs. Hive vs. JaguarDB

System Properties Comparison Amazon DynamoDB vs. Brytlyt vs. GeoMesa vs. Hive vs. JaguarDB

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Relational DBMS

Key-value store
Vector DBMS

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

docs.brytlyt.io

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

cwiki.apache.org/confluence/display/Hive/Home

www.jaguardb.com/support.html

Developer

Amazon

Brytlyt

CCRi and others

Apache Software Foundation

initially developed by Facebook

DataJaguar, Inc.

Initial release

2012

2016

2014

2012

2015

Current release

5.0, August 2023

4.0.5, February 2024

3.1.3, April 2022

3.3 July 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2

Open Source

GPL V3.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

Scala

Java

C++

the server part. Clients available in other languages

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java VM

Linux

Data scheme

schema-free

yes

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

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

RESTful HTTP API

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

JDBC
ODBC
Thrift

JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C++
Java
PHP
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

user defined functions and integration of map-reduce

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

depending on storage layer

selectable replication factor

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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.

depending on storage layer

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Access rights for users, groups and roles

rights management via user accounts

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.