DBMS > GeoMesa vs. MySQL vs. Sqrrl vs. WakandaDB

System Properties Comparison GeoMesa vs. MySQL vs. Sqrrl vs. WakandaDB

Please select another system to include it in the comparison.

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.

Widely used open source RDBMS

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

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

www.mysql.com

sqrrl.com

wakanda.github.io

Technical documentation

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

dev.mysql.com/doc

wakanda.github.io/doc

Developer

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

Amazon

originally Sqrrl Data, Inc.

Wakanda SAS

Initial release

2014

1995

2012

Current release

4.0.5, February 2024

8.4.0, April 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

C and C++

Java

C++, JavaScript

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

RESTful HTTP API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

making use of Hadoop

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

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

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Atomic updates per row, document, or graph entity

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.