DBMS > FatDB vs. LokiJS vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. RDFox

System Properties Comparison FatDB vs. LokiJS vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. RDFox

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

In-memory JavaScript DBMS

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

Globally distributed, horizontally scalable, multi-model database service

High performance knowledge graph and semantic reasoning engine

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS
RDF store

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Website

github.com/techfort/LokiJS

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

azure.microsoft.com/services/cosmos-db

www.oxfordsemantic.tech

Technical documentation

techfort.github.io/LokiJS

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.oxfordsemantic.tech

Developer

FatCloud

Microsoft

Oxford Semantic Technologies

Initial release

2012

2014

1992

2014

2017

Current release

1902 (16.0.11328.20222), March 2019

6.0, Septermber 2022

License

Commercial or Open Source

commercial

Open Source

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.

Implementation language

JavaScript

C++

Server operating systems

Windows

server-less, requires a JavaScript environment (browser, Node.js)

Windows

Not a real database server, but making use of DLLs

hosted

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

yes

RDF schemas

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

via views

yes

All properties auto-indexed by default

SQL

Support of SQL

Via inetgration in SQL Server

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API
SPARQL 1.1

Supported programming languages

JavaScript

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
Java

Server-side scripts

Stored procedures

yes

via applications

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

via applications

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

Implicit feature of the cloud service

replication via a shared file system

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single collection possible

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

Can implement custom security layer via applications

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

Access rights can be defined down to the item level

Roles, resources, and access types

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.