DBMS > GeoMesa vs. JSqlDb vs. Riak KV vs. SiteWhere vs. Transwarp KunDB

System Properties Comparison GeoMesa vs. JSqlDb vs. Riak KV vs. SiteWhere vs. Transwarp KunDB

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

JavaScript Query Language Database, stores JavaScript objects and primitives

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Spatial DBMS

Document store
Object oriented DBMS

Key-value store

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

Time Series DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.14
Rank	#341	Overall
	#149	Relational DBMS

Website

www.geomesa.org

jsqldb.org (offline)

github.com/sitewhere/sitewhere

www.transwarp.cn/en/product/kundb

Technical documentation

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

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

sitewhere1.sitewhere.io/index.html

Developer

CCRi and others

Konrad von Backstrom

OpenSource, formerly Basho Technologies

SiteWhere

Transwarp

Initial release

2014

2018

2009

2010

Current release

5.0.0, May 2024

0.8, December 2018

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

commercial

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.

Implementation language

Scala

Erlang

Java

Server operating systems

Linux
macOS
Windows

Linux
OS X

Linux
OS X
Windows

Data scheme

yes

schema-free

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

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

HTTP REST

Supported programming languages

JavaScript

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

Server-side scripts

Stored procedures

functions in JavaScript

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

none

Sharding

no "single point of failure"

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

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

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

using RocksDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

yes, using Riak Security

Users with fine-grained authorization concept

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.

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

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 to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

Basho Advances NoSQL Riak Enterprise 2.0 With Search, Advanced Data Types
15 September 2014, Data Center Knowledge

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page