DBMS > atoti vs. BoltDB vs. Riak KV vs. searchxml vs. TempoIQ

System Properties Comparison atoti vs. BoltDB vs. Riak KV vs. searchxml vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

An embedded key-value store for Go.

Distributed, fault tolerant key-value store

DBMS for structured and unstructured content wrapped with an application server

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Object oriented DBMS

Key-value store

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

Native XML DBMS
Search engine

Time Series DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

atoti.io

github.com/boltdb/bolt

www.searchxml.net/category/products

tempoiq.com (offline)

Technical documentation

docs.atoti.io

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

www.searchxml.net/support/handouts

Developer

ActiveViam

OpenSource, formerly Basho Technologies

informationpartners gmbh

TempoIQ

Initial release

2013

2009

2015

2012

Current release

3.2.0, December 2022

1.0

License

Commercial or Open Source

commercial

free versions available

Open Source

MIT License

Open Source

Apache version 2, commercial enterprise edition

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X

Windows

Data scheme

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

Multidimensional Expressions (MDX)

APIs and other access methods

HTTP API
Native Erlang Interface

RESTful HTTP API
WebDAV
XQuery
XSLT

HTTP API

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++

most other programming languages supported via APIs

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

Python

Erlang

yes

on the application server

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

Domain, group and role-based access control at the document level and for application services

simple authentication-based access control

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

FRTB product of the year: ActiveViam
28 November 2023, Risk.net

provided by Google News

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Three Reasons DevOps Should Consider Rocky Linux 9.4
15 May 2024, DevOps.com

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

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

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

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Share this page