DBMS > GeoMesa vs. Riak KV vs. SQream DB vs. ToroDB

System Properties Comparison GeoMesa vs. Riak KV vs. SQream DB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB 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.

Distributed, fault tolerant key-value store

a GPU-based, columnar RDBMS for big data analytics workloads

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Spatial DBMS

Key-value store

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

Relational DBMS

Document store

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.74
Rank	#224	Overall
	#103	Relational DBMS

Website

www.geomesa.org

sqream.com

github.com/torodb/server

Technical documentation

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

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

docs.sqream.com

Developer

CCRi and others

OpenSource, formerly Basho Technologies

SQream Technologies

8Kdata

Initial release

2014

2009

2017

2016

Current release

5.0.0, May 2024

3.2.0, December 2022

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

AGPL-V3

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

C++, CUDA, Haskell, Java, Scala

Java

Server operating systems

Linux
OS X

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

yes

string, integer, double, boolean, date, object_id

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

yes

APIs and other access methods

HTTP API
Native Erlang Interface

.Net
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++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions in Python

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

no "single point of failure"

horizontal and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

none

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

Eventual Consistency
Immediate 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

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

User concepts

Access control

yes

depending on the DBMS used for storage

yes, using Riak Security

Access rights for users and roles

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

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

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

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

I SQream, you SQream, we all SQream for … data analytics?
5 October 2023, fierce-network.com

SQream Announces Strategic Integration for Powerful Big Data Analytics with Dataiku
9 February 2024, insideBIGDATA

SQream Joins Samsung Cloud Platform Ecosystem
26 July 2023, Datanami

GPU data warehouse startup SQream lands $39.4M funding round
24 June 2020, SiliconANGLE News

SQream Technologies raises $39.4 million for GPU-accelerated databases
24 June 2020, VentureBeat

provided by Google News

Share this page