DBMS > H2GIS vs. Hazelcast vs. Interbase vs. Microsoft Access vs. Snowflake

System Properties Comparison H2GIS vs. Hazelcast vs. Interbase vs. Microsoft Access vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

A widely adopted in-memory data grid

Light-weight proven RDBMS

originally from Borland

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

Spatial DBMS

Key-value store

Relational DBMS

Secondary database models

Relational DBMS

Document store

JSON support with IMDG 3.12

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

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

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

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.h2gis.org

hazelcast.com

www.embarcadero.com/products/interbase

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

www.snowflake.com

Technical documentation

www.h2gis.org/docs/home

hazelcast.org/imdg/docs

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

CNRS

Hazelcast

Embarcadero

Microsoft

Snowflake Computing Inc.

Initial release

2013

2008

1984

1992

2014

Current release

5.3.6, November 2023

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

LGPL 3.0

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

All OS with a Java VM

Android
iOS
Linux
OS X
Windows

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

export as XML data possible

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

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Java

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

based on H2

yes

Event Listeners, Executor Services

yes

Interbase procedure and trigger language

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

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

yes

Replicated Map

Interbase Change Views

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

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

ACID

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, multi-version concurrency control (MVCC)

yes

Multiversion concurreny control

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

yes

based on H2

Role-based access control

fine grained access rights according to SQL-standard

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.