DBMS > Datomic vs. OpenQM vs. Riak KV vs. SiriDB

System Properties Comparison Datomic vs. OpenQM vs. Riak KV vs. SiriDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

QpenQM is a high-performance, self-tuning, multi-value DBMS

Distributed, fault tolerant key-value store

Open Source Time Series DBMS

Primary database model

Relational DBMS

Multivalue DBMS

Key-value store

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

Time Series DBMS

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

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

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

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Website

www.datomic.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

siridb.com

Technical documentation

docs.datomic.com

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

docs.siridb.com

Developer

Cognitect

Rocket Software, originally Martin Phillips

OpenSource, formerly Basho Technologies

Cesbit

Initial release

2012

1993

2009

2017

Current release

1.0.7180, July 2024

3.4-12

3.2.0, December 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPLv2, extended commercial license available

Open Source

Apache version 2, commercial enterprise edition

Open Source

MIT 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

Java, Clojure

Erlang

Server operating systems

All OS with a Java VM

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X

Linux

Data scheme

yes

with some exceptions

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data

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.

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

Clojure
Java

.Net
Basic
C
Java
Objective C
PHP
Python

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

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Erlang

Triggers

By using transaction functions

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

selectable replication factor

yes

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

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights can be defined down to the item level

yes, using Riak Security

simple rights management via user accounts

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

Brazil’s Nubank Acquires US Software Firm Cognitect
30 July 2020, Nearshore Americas

Lucas Cavalcanti on Using Clojure, Microservices, Hexagonal Architecture and Public Cloud at Nubank
16 August 2021, InfoQ.com

Brazil’s Nubank acquires US software firm Cognitect, creator of Clojure and Datomic
24 July 2020, LatamList

Nubank acquires US company; PayPal studies cryptocurrencies
24 July 2020, iupana.com

Zoona Case Study
16 December 2017, AWS Blog

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

Share this page