DBMS > KeyDB vs. Quasardb vs. SAP HANA vs. SiteWhere

System Properties Comparison KeyDB vs. Quasardb vs. SAP HANA vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Distributed, high-performance timeseries database

In-memory, column based data store. Available as appliance or cloud service

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.80
Rank	#219	Overall
	#31	Key-value stores

Score	0.19
Rank	#327	Overall
	#30	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

quasar.ai

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

Technical documentation

docs.keydb.dev

doc.quasar.ai/master

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

Developer

EQ Alpha Technology Ltd.

quasardb

SAP

SiteWhere

Initial release

2019

2009

2010

Current release

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

BSD-3

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

Linux

BSD
Linux
OS X
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

partial

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

yes

integer and binary

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

by using the Redis Search module

yes

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP API

JDBC
ODBC

HTTP REST

Supported programming languages

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

Lua

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

simple password-based access control and ACL

Cryptographically strong user authentication and audit trail

yes

Users with fine-grained authorization concept

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.