DBMS > AlaSQL vs. HarperDB vs. Microsoft SQL Server vs. NSDb vs. STSdb

System Properties Comparison AlaSQL vs. HarperDB vs. Microsoft SQL Server vs. NSDb vs. STSdb

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Microsofts flagship relational DBMS

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

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	0.55
Rank	#248	Overall
	#38	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

alasql.org

www.harperdb.io

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

nsdb.io

github.com/STSSoft/STSdb4

Technical documentation

github.com/AlaSQL/alasql

docs.harperdb.io/docs

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

nsdb.io/Architecture

Developer

Andrey Gershun & Mathias R. Wulff

HarperDB

Microsoft

STS Soft SC

Initial release

2014

2017

1989

2017

2011

Current release

3.1, August 2021

SQL Server 2022, November 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

MIT-License

commercial

free community edition available

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

Node.js

C++

Java, Scala

Server operating systems

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

Linux
OS X

Linux
Windows

Linux
macOS

Windows

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

yes

yes: int, bigint, decimal, string

yes

primitive types and user defined types (classes)

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 data manipulation statements

yes

SQL-like query language

APIs and other access methods

JavaScript API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

gRPC
HTTP REST
WebSocket

.NET Client API

Supported programming languages

JavaScript

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Java
Scala

C#
Java

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

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

A table resides as a whole on one (or more) nodes in a cluster

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

the nodes on which a table resides can be defined

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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 execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes, using LMDB

yes

Using Apache Lucene

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

Access rights for users and roles

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.