DBMS > AlaSQL vs. IBM Cloudant vs. IRONdb vs. Microsoft SQL Server vs. NSDb

System Properties Comparison AlaSQL vs. IBM Cloudant vs. IRONdb vs. Microsoft SQL Server vs. NSDb

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

JavaScript DBMS library

Database as a Service offering based on Apache CouchDB

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Microsofts flagship relational DBMS

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

Primary database model

Document store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

alasql.org

www.ibm.com/products/cloudant

www.circonus.com/solutions/time-series-database/

www.microsoft.com/en-us/sql-server

nsdb.io

Technical documentation

github.com/AlaSQL/alasql

cloud.ibm.com/docs/Cloudant

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/en-US/sql/sql-server

nsdb.io/Architecture

Developer

Andrey Gershun & Mathias R. Wulff

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Circonus LLC.

Microsoft

Initial release

2014

2010

2017

1989

2017

Current release

V0.10.20, January 2018

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

restricted free version is available

Open Source

Apache Version 2.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

JavaScript

Erlang

C and C++

C++

Java, Scala

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Linux

Linux
Windows

Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

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.

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL-like query language

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

gRPC
HTTP REST
WebSocket

Supported programming languages

JavaScript

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
Scala

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes, in Lua

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic, metric affinity per node

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Using Apache Lucene

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

fine grained access rights according to SQL-standard

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.