DBMS > Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. Sequoiadb vs. SiteWhere

System Properties Comparison Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. Sequoiadb vs. SiteWhere

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

NewSQL database with distributed OLTP and SQL

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Document store
Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

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

nsdb.io

origodb.com

www.sequoiadb.com

github.com/sitewhere/sitewhere

Technical documentation

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

nsdb.io/Architecture

origodb.com/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

sitewhere1.sitewhere.io/index.html

Developer

Microsoft

Robert Friberg et al

Sequoiadb Ltd.

SiteWhere

Initial release

2010

2017

2009

under the name LiveDB

2013

2010

Current release

V12

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Server: AGPL; Client: Apache V2

Open Source

Common Public Attribution License Version 1.0

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

C++

Java

Server operating systems

hosted

Linux
macOS

Linux
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

yes

oid, date, timestamp, binary, regex

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

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

HTTP REST

Supported programming languages

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

Java
Scala

.Net

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

Transact SQL

yes

JavaScript

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

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Role based authorization

simple password-based access control

Users with fine-grained authorization concept

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 migration to OCI - resources estimation and migration approach
11 January 2024, Oracle

Public Preview: New Azure SQL Database skills introduced to Microsoft Copilot in Azure | Azure updates
21 May 2024, Microsoft

Why migrate Windows Server and SQL Server to Azure: ROI, innovation, and free offers
25 April 2024, microsoft.com

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page