DBMS > Apache IoTDB vs. Microsoft Access vs. Microsoft SQL Server vs. Redis vs. Riak KV

System Properties Comparison Apache IoTDB vs. Microsoft Access vs. Microsoft SQL Server vs. Redis vs. Riak KV

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

Microsofts flagship relational DBMS

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.

Distributed, fault tolerant key-value store

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

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store
Graph DBMS
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	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

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

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

iotdb.apache.org

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

www.microsoft.com/en-us/sql-server

redis.com
redis.io

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

developer.microsoft.com/en-us/access

learn.microsoft.com/en-US/sql/sql-server

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Apache Software Foundation

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

OpenSource, formerly Basho Technologies

Initial release

2018

1992

1989

2009

Current release

1.1.0, April 2023

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

7.2.5, May 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

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

Open Source

Apache version 2, commercial enterprise edition

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

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

Implementation language

Java

C++

Erlang

Server operating systems

All OS with a Java VM (>= 1.8)

Windows

Not a real database server, but making use of DLLs

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X

Data scheme

yes

schema-free

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

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

restricted

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

yes

with RediSQL module

APIs and other access methods

JDBC
Native API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

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

Erlang

Triggers

yes

since Access 2010 using the ACE-engine

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

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

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

yes, but depending on the SQL-Server Edition

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

through RedisGears

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

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

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

but no files for transaction logging

ACID

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

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

In-memory capabilities

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

yes

User concepts

Access control

yes

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

yes, using Riak Security

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.