DBMS > Hazelcast vs. Ignite vs. Microsoft Access vs. Snowflake

System Properties Comparison Hazelcast vs. Ignite vs. Microsoft Access vs. Snowflake

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

hazelcast.com

ignite.apache.org

www.microsoft.com/en-us/microsoft-365/access

www.snowflake.com

Technical documentation

hazelcast.org/imdg/docs

apacheignite.readme.io/docs

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Hazelcast

Apache Software Foundation

Microsoft

Snowflake Computing Inc.

Initial release

2008

2015

1992

2014

Current release

5.3.6, November 2023

Apache Ignite 2.6

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

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++, Java, .Net

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

ANSI-99 for query and DML statements, subset of DDL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes (compute grid and cache interceptors can be used instead)

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

Events

yes (cache interceptors and events)

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes (replicated cache)

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

Security Hooks for custom implementations

a simple user-level security was built in till version Access 2003

Users with fine-grained authorization concept, user roles and pluggable authentication

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.