DBMS > 4D vs. BaseX vs. GigaSpaces vs. Microsoft Access vs. Redis

System Properties Comparison 4D vs. BaseX vs. GigaSpaces vs. Microsoft Access vs. Redis

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

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

Relational DBMS

Native XML DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Key-value store

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

Secondary database models

Graph DBMS
Search engine

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	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Website

www.4d.com

basex.org

www.gigaspaces.com

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

redis.com
redis.io

Technical documentation

developer.4d.com

docs.basex.org

docs.gigaspaces.com/latest/landing.html

developer.microsoft.com/en-us/access

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

Developer

4D, Inc

BaseX GmbH

Gigaspaces Technologies

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

1984

2007

2000

1992

2009

Current release

v20, April 2023

10.7, August 2023

15.5, September 2020

1902 (16.0.11328.20222), March 2019

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache Version 2; Commercial licenses available

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

Java

Java, C++, .Net

C++

Server operating systems

OS X
Windows

Linux
OS X
Windows

Linux
macOS
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports types

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.

yes

XML can be used for describing objects metadata

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

close to SQL 92

SQL-99 for query and DML statements

yes

but not compliant to any SQL standard

with RediSQL module

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

ADO.NET
DAO
ODBC
OLE DB

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

4D proprietary IDE
PHP

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

.Net
C++
Java
Python
Scala

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

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

yes

since Access 2010 using the ACE-engine

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

Triggers

yes

via events

yes, event driven architecture

yes

since Access 2010 using the ACE-engine

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

none

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

Map-Reduce pattern can be built with XAP task executors

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

ACID

multiple readers, single writer

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

but no files for transaction logging

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

Users and groups

Users with fine-grained authorization concept on 4 levels

Role-based access control

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.