DBMS > AlaSQL vs. Apache Druid vs. Microsoft SQL Server vs. Warp 10

System Properties Comparison AlaSQL vs. Apache Druid vs. Microsoft SQL Server vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Microsofts flagship relational DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Relational DBMS

Relational DBMS
Time Series DBMS

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	0.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

alasql.org

druid.apache.org

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

www.warp10.io

Technical documentation

github.com/AlaSQL/alasql

druid.apache.org/docs/latest/design

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

www.warp10.io/content/02_Getting_started

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation and contributors

Microsoft

SenX

Initial release

2014

2012

1989

2015

Current release

29.0.1, April 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache license v2

commercial

restricted free version is available

Open Source

Apache License 2.0

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

Java

C++

Java

Server operating systems

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

Linux
OS X
Unix

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-less columns are supported

yes

schema-free

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

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

SQL for querying

yes

APIs and other access methods

JavaScript API

JDBC
RESTful HTTP/JSON API

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

HTTP API
Jupyter
WebSocket

Supported programming languages

JavaScript

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

Server-side scripts

Stored procedures

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

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, via HDFS, S3 or other storage engines

yes, but depending on the SQL-Server Edition

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

none

Immediate Consistency

based on HBase

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

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

In-memory capabilities

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

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.