DBMS > BoltDB vs. Ignite vs. KeyDB vs. SAP HANA vs. Tkrzw

System Properties Comparison BoltDB vs. Ignite vs. KeyDB vs. SAP HANA vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Key-value store

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key-value store

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.74
Rank	#220	Overall
	#31	Key-value stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

github.com/boltdb/bolt

ignite.apache.org

github.com/Snapchat/KeyDB
keydb.dev

www.sap.com/products/hana.html

dbmx.net/tkrzw

Technical documentation

apacheignite.readme.io/docs

docs.keydb.dev

help.sap.com/hana

Developer

Apache Software Foundation

EQ Alpha Technology Ltd.

SAP

Mikio Hirabayashi

Initial release

2013

2015

2019

2010

2020

Current release

Apache Ignite 2.6

2.0 SPS07 (April 4, 2023), April 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

BSD-3

commercial

Open Source

Apache Version 2.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, .Net

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Appliance or cloud-service

Linux
macOS

Data scheme

schema-free

yes

schema-free

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

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

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Lua

SQLScript, R

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

yes

ACID

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

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

Security Hooks for custom implementations

simple password-based access control and ACL

yes

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.