DBMS > GeoMesa vs. Microsoft Azure Synapse Analytics vs. RocksDB vs. Sqrrl vs. Warp 10

System Properties Comparison GeoMesa vs. Microsoft Azure Synapse Analytics vs. RocksDB vs. Sqrrl vs. Warp 10

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

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Adaptable, secure NoSQL built on Apache Accumulo

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Spatial DBMS

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.geomesa.org

azure.microsoft.com/services/synapse-analytics

rocksdb.org

sqrrl.com

www.warp10.io

Technical documentation

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

docs.microsoft.com/azure/synapse-analytics

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

CCRi and others

Microsoft

Facebook, Inc.

Amazon

originally Sqrrl Data, Inc.

SenX

Initial release

2014

2016

2013

2012

2015

Current release

5.0.0, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

BSD

commercial

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

Scala

C++

Java

Server operating systems

hosted

Linux

Linux
OS X
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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

Actionscript
C

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

Server-side scripts

Stored procedures

Transact SQL

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding, horizontal partitioning

horizontal partitioning

Sharding

making use of Hadoop

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

selectable replication factor

making use of Hadoop

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

based on HBase

Foreign keys

Referential integrity

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

yes

Atomic updates per row, document, or graph entity

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

yes

User concepts

Access control

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)

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.