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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

A widely adopted in-memory data grid

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

Relational DBMS

Key-value store

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	1.73
Rank	#140	Overall
	#63	Relational DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.firebolt.io

hazelcast.com

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

www.snowflake.com

Technical documentation

docs.firebolt.io

hazelcast.org/imdg/docs

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Firebolt Analytics Inc.

Hazelcast

Microsoft

Snowflake Computing Inc.

Initial release

2020

2008

1992

2014

Current release

5.3.6, November 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

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++

Server operating systems

hosted

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

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

yes

SQL-like query language

yes

but not compliant to any SQL standard

yes

APIs and other access methods

.Net
ODBC
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Go
JavaScript (Node.js)
Python

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
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

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

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

depending on storage layer

yes

Replicated Map

none

yes

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

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

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.