DBMS > KeyDB vs. PouchDB vs. SAP HANA vs. Splunk

System Properties Comparison KeyDB vs. PouchDB vs. SAP HANA vs. Splunk

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

JavaScript DBMS with an API inspired by CouchDB

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

Analytics Platform for Big 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.70
Rank	#229	Overall
	#32	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

github.com/Snapchat/KeyDB
keydb.dev

pouchdb.com

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

docs.keydb.dev

pouchdb.com/guides

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

EQ Alpha Technology Ltd.

Apache Software Foundation

SAP

Splunk Inc.

Initial release

2019

2012

2010

2003

Current release

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

BSD-3

Open Source

commercial

Limited free edition and free developer edition available

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

JavaScript

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

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

by using the Redis Search module

yes

via views

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST

only for PouchDB Server
JavaScript 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

JavaScript

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

View functions in JavaScript

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency

Immediate Consistency

Eventual 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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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 IndexedDB, WebSQL or LevelDB as backend

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 and ACL

yes

Access rights for users and roles

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.