DBMS > Google Cloud Bigtable vs. NSDb vs. Riak TS vs. Yanza

System Properties Comparison Google Cloud Bigtable vs. NSDb vs. Riak TS 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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Wide column store

Time Series DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

cloud.google.com/bigtable

nsdb.io

yanza.com

Technical documentation

cloud.google.com/bigtable/docs

nsdb.io/Architecture

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

Developer

Google

Open Source, formerly Basho Technologies

Yanza

Initial release

2015

2017

2015

Current release

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

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

Java, Scala

Erlang

Server operating systems

hosted

Linux
macOS

Linux
OS X

Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes: int, bigint, decimal, string

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

all fields are automatically indexed

restricted

SQL

Support of SQL

SQL-like query language

yes, limited

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

gRPC
HTTP REST
WebSocket

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

Java
Scala

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

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

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

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

Google Launches Cloud Bigtable, A Highly Scalable And Performant NoSQL Database
6 May 2015, TechCrunch

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

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

provided by Google News

Share this page