DBMS > Amazon Redshift vs. GeoMesa vs. Microsoft Azure Synapse Analytics vs. Sqrrl vs. WakandaDB

System Properties Comparison Amazon Redshift vs. GeoMesa vs. Microsoft Azure Synapse Analytics vs. Sqrrl vs. WakandaDB

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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.

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Adaptable, secure NoSQL built on Apache Accumulo

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Score	0.09
Rank	#352	Overall
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

www.geomesa.org

azure.microsoft.com/services/synapse-analytics

sqrrl.com

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

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

docs.microsoft.com/azure/synapse-analytics

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

CCRi and others

Microsoft

Amazon

originally Sqrrl Data, Inc.

Wakanda SAS

Initial release

2012

2014

2016

2012

Current release

4.0.5, February 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

AGPLv3, extended 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

Scala

C++

Java

C++, JavaScript

Server operating systems

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

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.

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
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
PHP

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding, horizontal partitioning

Sharding

making use of Hadoop

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

selectable replication factor

making use of Hadoop

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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

yes

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

yes

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.