DBMS > GeoMesa vs. Riak KV vs. SpatiaLite vs. TDSQL for MySQL

System Properties Comparison GeoMesa vs. Riak KV vs. SpatiaLite vs. TDSQL for MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed, fault tolerant key-value store

Spatial extension of SQLite

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Spatial DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Score	0.96
Rank	#192	Overall
	#88	Relational DBMS

Website

www.geomesa.org

www.gaia-gis.it/fossil/libspatialite/index

www.tencentcloud.com/products/dcdb

Technical documentation

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

www.tiot.jp/riak-docs/riak/kv/latest

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.tencentcloud.com/document/product/1042

Developer

CCRi and others

OpenSource, formerly Basho Technologies

Alessandro Furieri

Tencent

Initial release

2014

2009

2008

2013

Current release

5.0.1, July 2024

3.2.0, December 2022

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

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

Erlang

C++

Server operating systems

Linux
OS X

server-less

hosted

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

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

no "single point of failure"

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

none

Multi-source replication
Source-replica replication

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

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, using Riak Security

Users with fine-grained authorization concept

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho aims for enterprise operational simplicity with new Data Platform
26 May 2015, diginomica

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

provided by Google News

Tencent Cloud Database recognised for cloud database management systems
21 December 2022, IT Brief Australia

Tencent Cloud partners Allo Bank to boost digital banking in Indonesia
5 July 2023, TechNode Global

Tencent Cloud Distributed Database Ranks First in the Growth Index: Frost & Sullivan's "2021 China Distributed Database Market Report" - PR Newswire APAC
16 May 2022, PR Newswire Asia

Allo Bank stirs up digital banking in Indonesia with Tencent Cloud
20 July 2023, Frontier Enterprise

Indonesia’s Allo Bank taps Tencent Cloud to enhance digital banking services
6 July 2023, FinTech Futures

provided by Google News

Share this page