DBMS > Hazelcast vs. Kinetica vs. Microsoft SQL Server vs. VoltDB

System Properties Comparison Hazelcast vs. Kinetica vs. Microsoft SQL Server vs. VoltDB

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

Fully vectorized database across both GPUs and CPUs

Microsofts flagship relational DBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1.46
Rank	#159	Overall
	#74	Relational DBMS

Website

hazelcast.com

www.kinetica.com

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

www.voltdb.com

Technical documentation

hazelcast.org/imdg/docs

docs.kinetica.com

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

docs.voltdb.com

Developer

Hazelcast

Kinetica

Microsoft

VoltDB Inc.

Initial release

2008

2012

1989

2010

Current release

5.3.6, November 2023

7.1, August 2021

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

C, C++

C++

Java, C++

Server operating systems

All OS with a Java VM

Linux

Linux
Windows

Linux
OS X

for development

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

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

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

Java

Triggers

yes

Events

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

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 or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

User concepts

Access control

Role-based access control

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.