DBMS > Hazelcast vs. KeyDB vs. SQLite vs. Trafodion

System Properties Comparison Hazelcast vs. KeyDB vs. SQLite vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

A widely adopted in-memory data grid

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

Widely used embeddable, in-process RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

github.com/Snapchat/KeyDB
keydb.dev

www.sqlite.org

trafodion.apache.org

Technical documentation

hazelcast.org/imdg/docs

docs.keydb.dev

www.sqlite.org/docs.html

trafodion.apache.org/documentation.html

Developer

Hazelcast

EQ Alpha Technology Ltd.

Dwayne Richard Hipp

Apache Software Foundation, originally developed by HP

Initial release

2008

2019

2000

2014

Current release

5.3.6, November 2023

3.46.1 (13 August 2024), August 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD-3

Open Source

Public Domain

Open Source

Apache 2.0

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.

Implementation language

Java

C++

C++, Java

Server operating systems

All OS with a Java VM

Linux

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

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

not rigid because of 'dynamic typing' concept.

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

the object must implement a serialization strategy

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Lua

Java Stored Procedures

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication
Source-replica replication

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

User concepts

Access control

Role-based access control

simple password-based access control and ACL

fine grained access rights according to SQL-standard

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.