DBMS > BigObject vs. Microsoft Azure Table Storage vs. Riak TS vs. ToroDB

System Properties Comparison BigObject vs. Microsoft Azure Table Storage vs. Riak TS vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Analytic DBMS for real-time computations and queries

A Wide Column Store for rapid development using massive semi-structured datasets

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Wide column store

Time Series DBMS

Document store

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

bigobject.io

azure.microsoft.com/en-us/services/storage/tables

github.com/torodb/server

Technical documentation

docs.bigobject.io

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

Developer

BigObject, Inc.

Microsoft

Open Source, formerly Basho Technologies

8Kdata

Initial release

2015

2012

2015

2016

Current release

3.0.0, September 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

AGPL-V3

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

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux
OS X

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

restricted

SQL

Support of SQL

SQL-like DML and DDL statements

yes, limited

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

Lua

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

links between datasets can be stored

Transaction concepts

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Access rights based on private key authentication or shared access signatures

Access rights for users and roles

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

Working with Azure to Use and Manage Data Lakes
7 March 2024, Simplilearn

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

Inside Azure File Storage
7 October 2015, Microsoft

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

provided by Google News

Share this page