DBMS > Microsoft Access vs. Redis vs. Sphinx vs. YugabyteDB

System Properties Comparison Microsoft Access vs. Redis vs. Sphinx vs. YugabyteDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Open source search engine for searching in data from different sources, e.g. relational databases

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Relational DBMS

Key-value store

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

Search engine

Relational DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Document store
Wide column store

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

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

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

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	3.11
Rank	#99	Overall
	#51	Relational DBMS

Website

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

redis.com
redis.io

sphinxsearch.com

www.yugabyte.com

Technical documentation

developer.microsoft.com/en-us/access

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

sphinxsearch.com/docs

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Sphinx Technologies Inc.

Yugabyte Inc.

Initial release

1992

2009

2001

2017

Current release

1902 (16.0.11328.20222), March 2019

7.2.4, January 2024

3.5.1, February 2023

2.19, September 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

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

Open Source

GPL version 2, commercial licence available

Open Source

Apache 2.0

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.

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

C++

C and C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X

Data scheme

yes

schema-free

yes

depending on used data model

Typing

predefined data types such as float or date

yes

partial

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

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

with RediSearch module

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

with RediSQL module

SQL-like query language (SphinxQL)

yes, PostgreSQL compatible

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

proprietary protocol

RESP - REdis Serialization Protocol

Proprietary protocol

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

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

yes

sql, plpgsql, C

Triggers

yes

since Access 2010 using the ACE-engine

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

Strong consistency on writes and tunable consistency on reads

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

Atomic execution of command blocks and scripts and optimistic locking

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

The original contents of fields are not stored in the Sphinx index.

yes

based on RocksDB

In-memory capabilities

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

yes

User concepts

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

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» 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.