DBMS > Datomic vs. Microsoft Access vs. Snowflake vs. TerarkDB

System Properties Comparison Datomic vs. Microsoft Access vs. Snowflake vs. TerarkDB

Please select another system to include it in the comparison.

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

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 key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Key-value store

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

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

www.datomic.com

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

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

docs.datomic.com

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Cognitect

Microsoft

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2012

1992

2014

2016

Current release

1.0.6735, June 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

limited edition free

commercial

Bundled with Microsoft Office

commercial

restricted open source version 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

Java, Clojure

C++

Server operating systems

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

hosted

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

APIs and other access methods

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

Clojure
Java

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

Transaction 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

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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.