DBMS > GridDB vs. Microsoft Azure Table Storage vs. NSDb vs. OrigoDB

System Properties Comparison GridDB vs. Microsoft Azure Table Storage vs. NSDb vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

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

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

A fully ACID in-memory object graph database

Primary database model

Time Series DBMS

Wide column store

Time Series DBMS

Document store
Object oriented DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

griddb.net

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

nsdb.io

origodb.com

Technical documentation

docs.griddb.net

nsdb.io/Architecture

origodb.com/docs

Developer

Toshiba Corporation

Microsoft

Robert Friberg et al

Initial release

2013

2012

2017

2009

under the name LiveDB

Current release

5.1, August 2022

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

Apache Version 2.0

Open Source

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

C++

Java, Scala

Server operating systems

Linux

hosted

Linux
macOS

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

RESTful HTTP API

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Java
Scala

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID at container level

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

Write ahead log

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 for users can be defined per database

Access rights based on private key authentication or shared access signatures

Role based authorization

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

Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data Management
3 December 2019, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

’s SQL Interface, Aims to Accelerate Open Innovation
17 June 2020, global.toshiba

TOSHIBA DIGITAL SOLUTIONS CORPORATION
1 November 2020, global.toshiba

IoT: Opt for the Right Open Source Database
11 August 2023, Open Source For You

provided by Google News

How to use Azure Table storage in .Net
10 July 2024, InfoWorld

Working with Azure to Use and Manage Data Lakes
23 July 2024, Simplilearn

Azure Cosmos DB Data Migration tool imports from Azure Table storage
5 May 2015, Microsoft

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

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

provided by Google News

Share this page