DBMS > Dragonfly vs. Ehcache vs. LevelDB vs. SQLite

System Properties Comparison Dragonfly vs. Ehcache vs. LevelDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

A widely adopted Java cache with tiered storage options

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Relational DBMS

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.ehcache.org

github.com/google/leveldb

www.sqlite.org

Technical documentation

www.dragonflydb.io/docs

www.ehcache.org/documentation

github.com/google/leveldb/blob/main/doc/index.md

www.sqlite.org/docs.html

Developer

DragonflyDB team and community contributors

Terracotta Inc, owned by Software AG

Google

Dwayne Richard Hipp

Initial release

2023

2009

2011

2000

Current release

1.0, March 2023

3.10.0, March 2022

1.23, February 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

Open Source

Public Domain

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

C++

Java

C++

Server operating systems

Linux

All OS with a Java VM

Illumos
Linux
OS X
Windows

server-less

Data scheme

scheme-free

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JCache

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

Server-side scripts

Stored procedures

Lua

Triggers

publish/subscribe channels provide some trigger functionality

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

via file-system locks

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

with automatic compression on writes

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

Password-based authentication

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.