DBMS > ArangoDB vs. Microsoft Access vs. Snowflake

System Properties Comparison ArangoDB vs. Microsoft Access vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native multi-model DBMS for graph, document, key/value and search. All in one engine and accessible with one query language.

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

Document store
Graph DBMS
Key-value store
Search engine

Relational DBMS

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

Score	3.77
Rank	#87	Overall
	#15	Document stores
	#5	Graph DBMS
	#12	Key-value stores
	#10	Search engines

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

arangodb.com

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

www.snowflake.com

Technical documentation

docs.arangodb.com

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Social network pages

Developer

ArangoDB Inc.

Microsoft

Snowflake Computing Inc.

Initial release

2012

1992

2014

Current release

3.11.5, November 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial license (Enterprise) 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.

ArangoDB Cloud –The Managed Cloud Service of ArangoDB. Provides fully managed, and monitored cluster deployments of any size, with enterprise-grade security. Get started for free and continue for as little as $0,21/hour.

Implementation language

C++

Server operating systems

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

automatically recognizes schema within a collection

yes

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

Typing

predefined data types such as float or date

yes

string, double, boolean, list, hash

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

AQL
Foxx Framework
Graph API (Gremlin)
GraphQL query language
HTTP API
Java & SpringData
JSON style queries
VelocyPack/VelocyStream

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Clojure
Elixir
Go
Java
JavaScript (Node.js)
PHP
Python
R
Rust

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

since version 2.0

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with configurable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be done with stored procedures in JavaScript

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

configurable per collection or per write
Immediate Consistency
OneShard (highly available, fault-tolerant deployment mode with ACID semantics)

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

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

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.

User concepts

Access control

yes

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

Specific characteristics

Graph and Beyond. With more than 11,000 stargazers on GitHub, ArangoDB is the leading...
» more

Competitive advantages

Consolidation: As a native multi-model database, can be used as a full blown document...
» more

Typical application scenarios

Native multi-model in ArangoDB is being used for a broad range of projects across...
» more

Key customers

Cisco, Barclays, Refinitive, Siemens Mentor, Kabbage, Liaison, Douglas, MakeMyTrip,...
» more

Market metrics

ArangoDB is the leading native multi-model database with over 11,000 stargazers on...
» more

Licensing and pricing models

Very permissive Apache 2 License for Community Edition & commercial licenses are...
» more

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.