DBMS > Apache Phoenix vs. Microsoft Access vs. OpenSearch vs. Realm

System Properties Comparison Apache Phoenix vs. Microsoft Access vs. OpenSearch vs. Realm

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

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 distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Relational DBMS

Search engine

Document store

Secondary database models

Vector DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

phoenix.apache.org

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

github.com/opensearch-project
opensearch.org

realm.io

Technical documentation

phoenix.apache.org

developer.microsoft.com/en-us/access

opensearch.org/docs/latest

realm.io/docs

Developer

Apache Software Foundation

Microsoft

Amazon Web Services

Realm, acquired by MongoDB in May 2019

Initial release

2014

1992

2021

2014

Current release

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

1902 (16.0.11328.20222), March 2019

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

Open Source

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.
Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

C++

Java

Server operating systems

Linux
Unix
Windows

Windows

Not a real database server, but making use of DLLs

All OS with a Java VM

Android
Backend: server-less
iOS
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

JDBC

ADO.NET
DAO
ODBC
OLE DB

Java API
RESTful HTTP/JSON API

Supported programming languages

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

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

since Access 2010 using the ACE-engine

yes

by using the 'percolation' feature

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

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

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

ACID

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

In-Memory realm

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

yes

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.