DBMS > Newts vs. Riak TS vs. Warp 10 vs. YDB

System Properties Comparison Newts vs. Riak TS vs. Warp 10 vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS based on Cassandra

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

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

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Time Series DBMS

Document store
Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

opennms.github.io/newts

www.warp10.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

github.com/OpenNMS/newts/wiki

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

www.warp10.io/content/02_Getting_started

ydb.tech/en/docs

Developer

OpenNMS Group

Open Source, formerly Basho Technologies

SenX

Yandex

Initial release

2014

2015

2019

Current release

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

Apache 2.0; commercial license available

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

Erlang

Java

Server operating systems

Linux
OS X
Windows

Linux
OS X

Linux
OS X
Windows

Linux

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, 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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes, limited

SQL-like query language (YQL)

APIs and other access methods

HTTP REST
Java API

HTTP API
Native Erlang Interface

HTTP API
Jupyter
WebSocket

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

Java

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

Erlang

yes

WarpScript

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

selectable replication factor

based on HBase

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

links between datasets 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

In-memory capabilities

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

yes

User concepts

Access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

Access rights defined for Yandex Cloud users

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

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Time Series Databases Software Market [2024-2031] | InfluxData, Trendalyze, Amazon Timestream
11 May 2024, Motions Online

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
24 April 2024, Amoré

Time Series Intelligence Software Market Analysis and Revenue Prediction | Azure Time Series Insights, Trendalyze ...
20 May 2024, Weekly Post Gazette

provided by Google News

Russian Court Sues Yandex CEO For LGBT Propaganda Case
30 April 2024, VOI.ID

Personal Data Protection Service Initiates Probe into Yandex.Go App’s Data Processing
10 August 2023, Civil Georgia

Data leak from Russian delivery app shows dining habits of the secret police
3 April 2022, The Verge

Yandex code leak: Why hack of ‘Russian Google’s’ ranking factors has spooked the SEO industry
1 February 2023, The Indian Express

Russian secret police data leaked by food delivery app including where they live and what they eat...
4 April 2022, The US Sun

provided by Google News

Share this page