DBMS > Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. VoltDB

System Properties Comparison Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering with high compatibility to Microsoft SQL Server

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

A fully ACID in-memory object graph database

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	1.46
Rank	#159	Overall
	#74	Relational DBMS

Website

azure.microsoft.com/en-us/products/azure-sql/database

nsdb.io

origodb.com

www.voltdb.com

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

nsdb.io/Architecture

origodb.com/docs

docs.voltdb.com

Developer

Microsoft

Robert Friberg et al

VoltDB Inc.

Initial release

2010

2017

2009

under the name LiveDB

2010

Current release

V12

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

hosted

Linux
macOS

Linux
Windows

Linux
OS X

for development

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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.

yes

can be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

Java
Scala

.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Transact SQL

yes

Java

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

depending on model

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

Write ahead log

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

Users and roles with access to stored procedures

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

DB-Engines blog posts

PostgreSQL is the DBMS of the Year 2020
4 January 2021, Paul Andlinger, Matthias Gelbmann

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

The popularity of cloud-based DBMSs has increased tenfold in four years
7 February 2017, Matthias Gelbmann

show all

Recent citations in the news

Copilot in Azure SQL Database in Private Preview
27 March 2024, InfoQ.com

Microsoft unveils Copilot for Azure SQL Database
27 March 2024, InfoWorld

Azure SQL Database takes Saturday off on US east coast following network power failure
18 September 2023, The Register

Expand the limits of innovation with Azure data
21 March 2024, Microsoft

Power what’s next with limitless relational databases from Azure
15 November 2023, Microsoft

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Combines Streaming, Global Data
1 February 2017, Datanami

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

provided by Google News

Share this page