DBMS > Amazon Redshift vs. GeoMesa vs. NSDb vs. Sadas Engine

System Properties Comparison Amazon Redshift vs. GeoMesa vs. NSDb vs. Sadas Engine

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

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

aws.amazon.com/redshift

www.geomesa.org

nsdb.io

www.sadasengine.com

Technical documentation

docs.aws.amazon.com/redshift

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

nsdb.io/Architecture

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Amazon (based on PostgreSQL)

CCRi and others

SADAS s.r.l.

Initial release

2012

2014

2017

2006

Current release

5.0.0, May 2024

8.0

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

free trial version 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

Scala

Java, Scala

C++

Server operating systems

hosted

Linux
macOS

AIX
Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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.

Secondary indexes

restricted

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

gRPC
HTTP REST
WebSocket

JDBC
ODBC
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

Java
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Eventual Consistency

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

Using Apache Lucene

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

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Access rights for users, groups and roles 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.