DBMS > Graph Engine vs. KairosDB vs. Microsoft Access vs. Redis vs. SAP SQL Anywhere

System Properties Comparison Graph Engine vs. KairosDB vs. Microsoft Access vs. Redis vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Distributed Time Series DBMS based on Cassandra or H2

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.

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Graph DBMS
Key-value store

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

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

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.graphengine.io

github.com/kairosdb/kairosdb

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

redis.com
redis.io

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.graphengine.io/docs/manual

kairosdb.github.io

developer.microsoft.com/en-us/access

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SAP

formerly Sybase

Initial release

2010

2013

1992

2009

1992

Current release

1.2.2, November 2018

1902 (16.0.11328.20222), March 2019

7.2.4, January 2024

17, July 2015

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

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

commercial

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

.NET and C

Java

C++

Server operating systems

.NET

Linux
OS X
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.

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

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.

yes

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

with RediSQL module

yes

APIs and other access methods

RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET
DAO
ODBC
OLE DB

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C#
C++
F#
Visual Basic

Java
JavaScript

Node.js
PHP
Python

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
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

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

yes, in C/C++, Java, .Net or Perl

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

horizontal partitioning

Sharding

based on Cassandra

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Immediate Consistency

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

but no files for transaction logging

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

yes

User concepts

Access control

simple password-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

fine grained access rights according to SQL-standard

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.