DBMS > Hazelcast vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Spark SQL

System Properties Comparison Hazelcast vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Key-value store

Wide column store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
Spatial DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

hazelcast.com

azure.microsoft.com/en-us/services/storage/tables

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

spark.apache.org/sql

Technical documentation

hazelcast.org/imdg/docs

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

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Hazelcast

Microsoft

Apache Software Foundation

Initial release

2008

2012

1989

2014

Current release

5.3.6, November 2023

SQL Server 2022, November 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

Open Source

Apache 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

Java

C++

Scala

Server operating systems

All OS with a Java VM

hosted

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-like DML and DDL statements

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

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

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

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

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Role-based access control

Access rights based on private key authentication or shared access signatures

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.