DBMS > Datomic vs. EXASOL vs. Microsoft Access vs. Snowflake vs. SurrealDB

System Properties Comparison Datomic vs. EXASOL vs. Microsoft Access vs. Snowflake vs. SurrealDB

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Relational DBMS

Document store
Graph DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

www.datomic.com

www.exasol.com

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

www.snowflake.com

surrealdb.com

Technical documentation

docs.datomic.com

www.exasol.com/resources

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

surrealdb.com/docs

Developer

Cognitect

Exasol

Microsoft

Snowflake Computing Inc.

SurrealDB Ltd

Initial release

2012

2000

1992

2014

2022

Current release

1.0.6735, June 2023

1902 (16.0.11328.20222), March 2019

v1.5.0, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Bundled with Microsoft Office

commercial

Open Source

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, Clojure

C++

Rust

Server operating systems

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

hosted

Linux
macOS
Windows

Data scheme

yes

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

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL-like query language

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

Clojure
Java

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

By using transaction functions

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

But extensive use of caching in the application peers

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

User concepts

Access control

Access rights for users, groups and roles 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

yes, based on authentication and database rules

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.