DBMS > Fauna vs. Microsoft Access vs. OrigoDB vs. Snowflake

System Properties Comparison Fauna vs. Microsoft Access vs. OrigoDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

A fully ACID in-memory object graph database

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

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

Score	1.55
Rank	#154	Overall
	#26	Document stores
	#14	Graph DBMS
	#72	Relational DBMS
	#13	Time Series DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

fauna.com

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

origodb.com

www.snowflake.com

Technical documentation

docs.fauna.com

developer.microsoft.com/en-us/access

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

Fauna, Inc.

Microsoft

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2014

1992

2009

under the name LiveDB

2014

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

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.

Implementation language

Scala

C++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

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

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

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

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

yes

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

consistent hashing

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Source-replica replication

yes

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

depending on model

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

Write ahead log

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

Identity management, authentication, and access control

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

Role based authorization

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.