DBMS > OrigoDB vs. Riak KV vs. Warp 10 vs. Yanza

System Properties Comparison OrigoDB vs. Riak KV vs. Warp 10 vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A fully ACID in-memory object graph database

Distributed, fault tolerant key-value store

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Time Series DBMS for IoT Applications

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

Time Series DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

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

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

origodb.com

www.warp10.io

yanza.com

Technical documentation

origodb.com/docs

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

www.warp10.io/content/02_Getting_started

Developer

Robert Friberg et al

OpenSource, formerly Basho Technologies

SenX

Yanza

Initial release

2009

under the name LiveDB

2009

2015

Current release

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache License 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

Java

Server operating systems

Linux
Windows

Linux
OS X

Linux
OS X
Windows

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

Secondary indexes

yes

restricted

SQL

Support of SQL

APIs and other access methods

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

HTTP API
Jupyter
WebSocket

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Erlang

yes

WarpScript

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

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"

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on HBase

none

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

based on HBase

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

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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

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

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

Basho Advances NoSQL Riak Enterprise 2.0 With Search, Advanced Data Types
15 September 2014, Data Center Knowledge

provided by Google News

Time Series Databases Software market latest trends, CAGR, and forecast till 2026 | eSherpa Market Reports
13 April 2020, openPR

provided by Google News

Share this page