DBMS > Amazon Redshift vs. CouchDB vs. Ehcache vs. LeanXcale vs. Microsoft Access

System Properties Comparison Amazon Redshift vs. CouchDB vs. Ehcache vs. LeanXcale vs. Microsoft Access

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A widely adopted Java cache with tiered storage options

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

Primary database model

Relational DBMS

Document store

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/redshift

couchdb.apache.org

www.ehcache.org

www.leanxcale.com

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

Technical documentation

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

www.ehcache.org/documentation

developer.microsoft.com/en-us/access

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Terracotta Inc, owned by Software AG

LeanXcale

Microsoft

Initial release

2012

2005

2009

2015

1992

Current release

3.3.3, December 2023

3.10.0, March 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

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

Erlang

Java

C++

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Data scheme

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

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

through Apache Derby

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

JCache

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java

C
Java
Scala

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

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

atomic operations within a single document possible

yes

supports JTA and can work as an XA resource

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

but no files for transaction logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.