DBMS > LMDB vs. Riak KV vs. SiteWhere vs. Transbase

System Properties Comparison LMDB vs. Riak KV vs. SiteWhere vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performant, light-weight, embedded key-value database library

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

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	1.94
Rank	#120	Overall
	#20	Key-value stores

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

www.symas.com/symas-embedded-database-lmdb

github.com/sitewhere/sitewhere

www.transaction.de/en/products/transbase.html

Technical documentation

www.lmdb.tech/doc

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

sitewhere1.sitewhere.io/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Symas

OpenSource, formerly Basho Technologies

SiteWhere

Transaction Software GmbH

Initial release

2011

2009

2010

1987

Current release

0.9.32, January 2024

3.2.0, December 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

commercial

free development license

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

Erlang

Java

C and C++

Server operating systems

Linux
Unix
Windows

Linux
OS X

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

yes

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.

yes

User concepts

Access control

yes, using Riak Security

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

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

Recent citations in the news

Threat Actors Exploit Multiple Vulnerabilities in Ivanti Connect Secure and Policy Secure Gateways
29 February 2024, CISA

The Lightning Memory-mapped Database
2 March 2016, InfoQ.com

Akamai launches managed database service
25 April 2022, Blocks & Files

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

The Tom Brady Data Biography
8 September 2023, StatsBomb

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

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Basho aims for enterprise operational simplicity with new Data Platform
26 May 2015, diginomica

provided by Google News

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

Top Open-Source Tools for IoT Development in 2024
5 September 2024, Analytics Insight

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

provided by Google News

Share this page