DBMS > Axibase vs. GeoSpock vs. Microsoft Access vs. Postgres-XL vs. Redis

System Properties Comparison Axibase vs. GeoSpock vs. Microsoft Access vs. Postgres-XL vs. Redis

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Spatial and temporal data processing engine for extreme data scale

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Time Series DBMS

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

Time Series DBMS

Document store
Spatial DBMS

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.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

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

Website

axibase.com/docs/atsd/finance

geospock.com

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

www.postgres-xl.org

redis.com
redis.io

Technical documentation

developer.microsoft.com/en-us/access

www.postgres-xl.org/documentation

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

Developer

Axibase Corporation

GeoSpock

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2013

1992

2014

since 2012, originally named StormDB

2009

Current release

15585

2.0, September 2019

1902 (16.0.11328.20222), March 2019

10 R1, October 2018

7.2.4, January 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Bundled with Microsoft Office

Open Source

Mozilla public license

Open Source

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

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.

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

Implementation language

Java

Java, Javascript

C++

Server operating systems

Linux

hosted

Windows

Not a real database server, but making use of DLLs

Linux
macOS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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 type, but no XML query functionality

Secondary indexes

temporal, categorical

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

yes

distributed, parallel query execution

with RediSQL module

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Go
Java
PHP
Python
R
Ruby

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

user defined functions

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

Sharding

Automatic sharding

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

ACID

but no files for transaction logging

ACID

MVCC

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

Access rights for users can be defined per table

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

fine grained access rights according to SQL-standard

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.