DBMS > InfluxDB vs. KairosDB vs. Microsoft Access vs. Redis vs. TerarkDB

System Properties Comparison InfluxDB vs. KairosDB vs. Microsoft Access vs. Redis vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

DBMS for storing time series, events and metrics

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.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Secondary database models

Spatial DBMS

with GEO package

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	25.83
Rank	#28	Overall
	#1	Time Series DBMS

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	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.influxdata.com/products/influxdb-overview

github.com/kairosdb/kairosdb

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

redis.com
redis.io

github.com/bytedance/terarkdb

Technical documentation

docs.influxdata.com/influxdb

kairosdb.github.io

developer.microsoft.com/en-us/access

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

ByteDance, originally Terark

Initial release

2013

1992

2009

2016

Current release

2.7.6, April 2024

1.2.2, November 2018

1902 (16.0.11328.20222), March 2019

7.2.4, January 2024

License

Commercial or Open Source

Open Source

MIT-License; commercial enterprise version available

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

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

commercial

restricted open source version available

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

C++

Server operating systems

Linux
OS X

through Homebrew

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.

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

Numeric data and Strings

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.

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

with RediSQL module

APIs and other access methods

HTTP API
JSON over UDP

Graphite protocol
HTTP REST
Telnet API

ADO.NET
DAO
ODBC
OLE DB

proprietary protocol

RESP - REdis Serialization Protocol

C++ API
Java API

Supported programming languages

.Net
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Perl
PHP
Python
R
Ruby
Rust
Scala

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++
Java

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

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

Sharding

in enterprise version only

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

in enterprise version only

selectable replication factor

based on Cassandra

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

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

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

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

Depending on used storage engine

yes

User concepts

Access control

simple rights management via user accounts

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

More information provided by the system vendor

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

News

Efficiency Unleashed: Streamlining Workflows with the InfluxDB Management API
23 May 2024

What is DevRel at InfluxData
21 May 2024

An Introductory Guide to Grafana Alerts
16 May 2024

What to Expect When You’re Expecting InfluxDB: A Guide
14 May 2024

Introduction to Apache Iceberg
9 May 2024

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.