DBMS > Apache Phoenix vs. LMDB vs. Microsoft Access vs. Spark SQL

System Properties Comparison Apache Phoenix vs. LMDB vs. Microsoft Access vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A high performant, light-weight, embedded key-value database library

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	3.01
Rank	#103	Overall
	#52	Relational DBMS

Score	2.44
Rank	#117	Overall
	#22	Key-value stores

Score	143.44
Rank	#9	Overall
	#6	Relational DBMS

Score	22.86
Rank	#35	Overall
	#21	Relational DBMS

Website

phoenix.apache.org

www.symas.com/symas-embedded-database-lmdb

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

spark.apache.org/sql

Technical documentation

phoenix.apache.org

developer.microsoft.com/en-us/access

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Apache Software Foundation

Symas

Microsoft

Apache Software Foundation

Initial release

2014

2011

1992

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

0.9.29, March 2021

1902 (16.0.11328.20222), March 2019

3.2.0, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache 2.0

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

Java

C++

Scala

Server operating systems

Linux
Unix
Windows

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements

APIs and other access methods

JDBC

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

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

Sharding

none

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

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.