DBMS > LokiJS vs. MaxDB vs. Microsoft Access vs. RocksDB vs. Sadas Engine

System Properties Comparison LokiJS vs. MaxDB vs. Microsoft Access vs. RocksDB vs. Sadas Engine

Editorial information provided by DB-Engines

Name

Description

In-memory JavaScript DBMS

A robust and reliable RDBMS optimized to run all major SAP solutions

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

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

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

github.com/techfort/LokiJS

maxdb.sap.com

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

rocksdb.org

www.sadasengine.com

Technical documentation

techfort.github.io/LokiJS

maxdb.sap.com/documentation

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

Facebook, Inc.

SADAS s.r.l.

Initial release

2014

1984

1992

2013

2006

Current release

7.9.10.12, February 2024

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

8.0

License

Commercial or Open Source

Open Source

commercial

Limited community edition free

commercial

Bundled with Microsoft Office

Open Source

BSD

commercial

free trial version available

Cloud-based only

Only available as a cloud service

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

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

AIX
HP-UX
Linux
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

Linux

AIX
Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

JDBC
ODBC
Proprietary protocol

Supported programming languages

JavaScript

.Net
C#
Java
Perl
PHP
Python

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

yes

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

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights for users, groups and roles according to SQL-standard

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.