DBMS > GeoMesa vs. Immudb vs. Linter vs. Riak KV

System Properties Comparison GeoMesa vs. Immudb vs. Linter vs. Riak KV

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.

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

RDBMS for high security requirements

Distributed, fault tolerant key-value store

Primary database model

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

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.31
Rank	#295	Overall
	#42	Key-value stores

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

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

Website

www.geomesa.org

github.com/codenotary/immudb
immudb.io

linter.ru

Technical documentation

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

docs.immudb.io

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

Developer

CCRi and others

Codenotary

relex.ru

OpenSource, formerly Basho Technologies

Initial release

2014

2020

1990

2009

Current release

5.0.0, May 2024

1.2.3, April 2022

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

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

C and C++

Erlang

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X

Data scheme

yes

schema-free

yes

schema-free

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

SQL

Support of SQL

SQL-like syntax

yes

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

HTTP API
Native Erlang Interface

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

yes

proprietary syntax with the possibility to convert from PL/SQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

selectable replication factor

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

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

fine grained access rights according to SQL-standard

yes, using Riak Security

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

Codenotary brings its immutable database to the cloud
21 June 2023, TechCrunch

ImmuDB and Codenotary: It's a database, but the company isn't
20 December 2021, ZDNet

Immudb: Open-source database, built on a zero trust model
17 December 2021, Help Net Security

How Open-Source Database immudb Plans to Handle All That Metaverse Data
10 October 2022, Acceleration Economy

immudb (immutable database) 'tamper-proof' database - Open Source Insider
14 December 2021, ComputerWeekly.com

provided by Google 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 launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Share this page