DBMS > OrigoDB vs. Riak KV vs. searchxml vs. TempoIQ

System Properties Comparison OrigoDB vs. Riak KV vs. searchxml vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A fully ACID in-memory object graph database

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

Document store
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.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

origodb.com

www.searchxml.net/category/products

tempoiq.com (offline)

Technical documentation

origodb.com/docs

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

www.searchxml.net/support/handouts

Developer

Robert Friberg et al

OpenSource, formerly Basho Technologies

informationpartners gmbh

TempoIQ

Initial release

2009

under the name LiveDB

2009

2015

2012

Current release

3.2.0, December 2022

1.0

License

Commercial or Open Source

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

Erlang

C++

Server operating systems

Linux
Windows

Linux
OS X

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

APIs and other access methods

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

RESTful HTTP API
WebDAV
XQuery
XSLT

HTTP API

Supported programming languages

.Net

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

yes

Erlang

yes

on the application server

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

links between data sets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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

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

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

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

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Share this page