DBMS > GeoMesa vs. Riak KV vs. Sadas Engine vs. VelocityDB

System Properties Comparison GeoMesa vs. Riak KV vs. Sadas Engine vs. VelocityDB

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

SADAS Engine is a columnar DBMS specifically designed for high performance in Data warehouse environments

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Spatial DBMS

Key-value store

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

Relational DBMS

Graph DBMS
Object oriented DBMS

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

Score	0.78
Rank	#199	Overall
	#3	Spatial DBMS

Score	6.63
Rank	#64	Overall
	#8	Key-value stores

Score	0.00
Rank	#354	Overall
	#152	Relational DBMS

Score	0.03
Rank	#336	Overall
	#35	Graph DBMS
	#17	Object oriented DBMS

Website

www.geomesa.org

riak.com/products/riak-kv

www.sadasengine.com

velocitydb.com

Technical documentation

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

www.sadasengine.com/index.php/downloads/documentation-columnar-db

velocitydb.com/UserGuide

Developer

CCRi and others

Basho Technologies

SADAS s.r.l.

VelocityDB Inc

Initial release

2014

2009

2006

2011

Current release

3.2.0, April 2021

2.1.0, April 2015

8.0

7.x

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

free trial version available

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

C++

Server operating systems

Linux
OS X

AIX
Linux
Windows

Any that supports .NET

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
Proprietary protocol

.Net

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

.Net

Server-side scripts

Stored procedures

JavaScript and Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

no "single point of failure"

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

managed by 'Learn by Usage'

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users, groups and roles according to SQL-standard

Based on Windows Authentication

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

Oren Eini on RavenDB, including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

Is Riak A Good NoSQL Database Option?
1 July 2019, Analytics India Magazine

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

Basho’s database downfall highlights danger of bringing too-niche tech to market
10 July 2018, TechRepublic

provided by Google News

Job opportunities

Cloud Support Engineer I - Databases, Premium Support
Amazon Web Services, Inc., Remote

Cloud Support Engineer I - Databases
Amazon Web Services, Inc., Austin, TX

Software Developer
MOZ Group, Remote

Principal Engineer
Iron Mountain, Boston, MA

Back End Developer
Tietronix, Houston, TX

jobs by

Share this page