DBMS > Amazon Redshift vs. Apache Phoenix vs. GridDB vs. Microsoft Access vs. Realm

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. GridDB vs. Microsoft Access vs. Realm

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Scalable in-memory time series database optimized for IoT and Big Data

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 DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Secondary database models

Key-value store
Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

aws.amazon.com/redshift

phoenix.apache.org

griddb.net

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

realm.io

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

docs.griddb.net

developer.microsoft.com/en-us/access

realm.io/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Toshiba Corporation

Microsoft

Realm, acquired by MongoDB in May 2019

Initial release

2012

2014

2013

1992

2014

Current release

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

5.1, August 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Bundled with Microsoft Office

Open Source

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

Java

C++

Server operating systems

hosted

Linux
Unix
Windows

Linux

Windows

Not a real database server, but making use of DLLs

Android
Backend: server-less
iOS
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92, SQL-like TQL (Toshiba Query Language)

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

since Access 2010 using the ACE-engine

runs within the applications so server-side scripts are unnecessary

Triggers

yes

since Access 2010 using the ACE-engine

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

ACID at container level

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

fine grained access rights according to SQL-standard

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

Access rights for users can be defined per database

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

yes

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.