DBMS > BigObject vs. Hazelcast vs. Microsoft Access vs. SAP HANA

System Properties Comparison BigObject vs. Hazelcast vs. Microsoft Access vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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.)

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

bigobject.io

hazelcast.com

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

www.sap.com/products/hana.html

Technical documentation

docs.bigobject.io

hazelcast.org/imdg/docs

developer.microsoft.com/en-us/access

help.sap.com/hana

Developer

BigObject, Inc.

Hazelcast

Microsoft

SAP

Initial release

2015

2008

1992

2010

Current release

5.3.6, November 2023

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Appliance or cloud-service

Data scheme

yes

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

but not compliant to any SQL standard

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

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

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

Server-side scripts

Stored procedures

Lua

yes

Event Listeners, Executor Services

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

yes

Events

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

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

yes

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.