DBMS > HarperDB vs. HBase vs. Microsoft Access vs. PouchDB vs. Redis

System Properties Comparison HarperDB vs. HBase vs. Microsoft Access vs. PouchDB vs. Redis

Editorial information provided by DB-Engines

Name

Description

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

JavaScript DBMS with an API inspired by CouchDB

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Primary database model

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	155.94
Rank	#6	Overall
	#1	Key-value stores

Website

www.harperdb.io

hbase.apache.org

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

pouchdb.com

redis.com
redis.io

Technical documentation

docs.harperdb.io/docs

hbase.apache.org/book.html

developer.microsoft.com/en-us/access

pouchdb.com/guides

docs.redis.com/latest/index.html
redis.io/docs

Developer

HarperDB

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2017

2008

1992

2012

2009

Current release

3.1, August 2021

2.3.4, January 2021

1902 (16.0.11328.20222), March 2019

7.1.1, June 2019

7.2.5, May 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Node.js

Java

C++

JavaScript

Server operating systems

Linux
OS X

Linux
Unix
Windows

using Cygwin

Windows

Not a real database server, but making use of DLLs

server-less, requires a JavaScript environment (browser, Node.js)

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

dynamic schema

schema-free, schema definition possible

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

options to bring your own types, AVRO

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

via views

yes

with RediSearch module

SQL

Support of SQL

SQL-like data manipulation statements

yes

but not compliant to any SQL standard

with RediSQL module

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Java API
RESTful HTTP API
Thrift

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

JavaScript

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

Coprocessors in Java

yes

since Access 2010 using the ACE-engine

View functions in JavaScript

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes

since Access 2010 using the ACE-engine

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Eventual Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

Single row ACID (across millions of columns)

ACID

but no files for transaction logging

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes, using LMDB

yes

but no files for transaction logging

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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 rights for users and roles

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

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.