DBMS > Amazon DynamoDB vs. Faircom DB vs. Hazelcast vs. Microsoft Access vs. Splice Machine

System Properties Comparison Amazon DynamoDB vs. Faircom DB vs. Hazelcast vs. Microsoft Access vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Document store
Key-value store

Key-value store
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	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

aws.amazon.com/dynamodb

www.faircom.com/products/faircom-db

hazelcast.com

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

splicemachine.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

hazelcast.org/imdg/docs

developer.microsoft.com/en-us/access

splicemachine.com/how-it-works

Developer

Amazon

FairCom Corporation

Hazelcast

Microsoft

Splice Machine

Initial release

2012

1979

2008

1992

2014

Current release

V12, November 2020

5.3.6, November 2023

1902 (16.0.11328.20222), March 2019

3.1, March 2021

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Restricted, free version available

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

Open Source

AGPL 3.0, commercial license available

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

ANSI C, C++

Java

C++

Java

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Solaris
Windows

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

yes, ANSI SQL with proprietary extensions

SQL-like query language

yes

but not compliant to any SQL standard

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

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

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Event Listeners, Executor Services

yes

since Access 2010 using the ACE-engine

yes

Java

Triggers

yes

by integration with AWS Lambda

yes

Events

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

Replicated Map

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

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

ACID across one or more tables within a single AWS account and region

tunable from ACID to Eventually Consistent

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Fine grained access rights according to SQL-standard with additional protections for files

Role-based access control

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

Access rights for users, groups and roles according to SQL-standard

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.