DBMS > LokiJS vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Oracle NoSQL

System Properties Comparison LokiJS vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Oracle NoSQL

Editorial information provided by DB-Engines

Name

Description

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

Fully managed big data interactive analytics platform

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

github.com/techfort/LokiJS

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

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

techfort.github.io/LokiJS

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/data-explorer

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Microsoft

Oracle

Initial release

2014

1992

2014

2019

2011

Current release

1902 (16.0.11328.20222), March 2019

cloud service with continuous releases

23.3, December 2023

License

Commercial or Open Source

Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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++

Java

Server operating systems

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

Windows

Not a real database server, but making use of DLLs

hosted

Linux
Solaris SPARC/x86

Data scheme

schema-free

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

JSON types

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

optional

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

via views

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

Kusto Query Language (KQL), SQL subset

SQL-like DML and DDL statements

APIs and other access methods

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

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

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

RESTful HTTP API

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

Yes, possible languages: KQL, Python, R

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Spark connector (open source): github.com/Azure/azure-kusto-spark

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

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

Access rights can be defined down to the item level

Azure Active Directory Authentication

Access rights for users and roles

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.