DBMS > FatDB vs. GeoMesa vs. Riak KV vs. STSdb vs. TempoIQ

System Properties Comparison FatDB vs. GeoMesa vs. Riak KV vs. STSdb vs. TempoIQ

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Key-value store

Spatial DBMS

Key-value store

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

Key-value store

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.geomesa.org

github.com/STSSoft/STSdb4

tempoiq.com (offline)

Technical documentation

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

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

Developer

FatCloud

CCRi and others

OpenSource, formerly Basho Technologies

STS Soft SC

TempoIQ

Initial release

2012

2014

2009

2011

2012

Current release

4.0.5, February 2024

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

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

Server operating systems

Windows

Linux
OS X

Windows

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Native Erlang Interface

.NET Client API

HTTP API

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#
Java

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Erlang

Triggers

yes

via applications

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

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

User concepts

Access control

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

yes, using Riak Security

simple authentication-based access control

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

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

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Share this page