DBMS > Amazon Redshift vs. Blueflood vs. GeoMesa

System Properties Comparison Amazon Redshift vs. Blueflood vs. GeoMesa

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 TimeSeries DBMS based on Cassandra

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

Primary database model

Relational DBMS

Time Series DBMS

Spatial DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.09
Rank	#353	Overall
	#33	Time Series DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Website

aws.amazon.com/redshift

blueflood.io

www.geomesa.org

Technical documentation

docs.aws.amazon.com/redshift

github.com/rax-maas/blueflood/wiki

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

Developer

Amazon (based on PostgreSQL)

Rackspace

CCRi and others

Initial release

2012

2013

2014

Current release

4.0.5, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache License 2.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

Java

Scala

Server operating systems

hosted

Linux
OS X

Data scheme

yes

predefined scheme

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

depending on storage layer

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

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.