DBMS > Graph Engine vs. LeanXcale vs. Microsoft Access vs. Microsoft Azure Table Storage vs. RocksDB

System Properties Comparison Graph Engine vs. LeanXcale vs. Microsoft Access vs. Microsoft Azure Table Storage vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

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 Wide Column Store for rapid development using massive semi-structured datasets

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

Primary database model

Graph DBMS
Key-value store

Key-value store
Relational DBMS

Relational DBMS

Wide column store

Key-value store

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

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

Website

www.graphengine.io

www.leanxcale.com

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

azure.microsoft.com/en-us/services/storage/tables

rocksdb.org

Technical documentation

www.graphengine.io/docs/manual

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

Microsoft

LeanXcale

Microsoft

Facebook, Inc.

Initial release

2010

2015

1992

2012

2013

Current release

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Bundled with Microsoft Office

commercial

Open Source

BSD

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

.NET and C

C++

Server operating systems

.NET

Windows

Not a real database server, but making use of DLLs

hosted

Linux

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

through Apache Derby

yes

but not compliant to any SQL standard

APIs and other access methods

RESTful HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

C++ API
Java API

Supported programming languages

C#
C++
F#
Visual Basic

C
Java
Scala

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

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

horizontal partitioning

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

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

Transaction concepts

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

ACID

but no files for transaction logging

optimistic locking

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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

Access rights based on private key authentication or shared access signatures

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.