DBMS > Apache Drill vs. KeyDB vs. Lovefield vs. Tkrzw

System Properties Comparison Apache Drill vs. KeyDB vs. Lovefield vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Embeddable relational database for web apps written in pure JavaScript

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

Document store
Relational DBMS

Key-value store

Relational DBMS

Key-value store

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

drill.apache.org

github.com/Snapchat/KeyDB
keydb.dev

google.github.io/lovefield

dbmx.net/tkrzw

Technical documentation

drill.apache.org/docs

docs.keydb.dev

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Apache Software Foundation

EQ Alpha Technology Ltd.

Google

Mikio Hirabayashi

Initial release

2012

2019

2014

2020

Current release

1.20.3, January 2023

2.1.12, February 2017

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

BSD-3

Open Source

Apache 2.0

Open Source

Apache Version 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

C++

JavaScript

C++

Server operating systems

Linux
OS X
Windows

Linux

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

tested with Chrome, Firefox, IE, Safari

Linux
macOS

Data scheme

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.

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

C++

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

Server-side scripts

Stored procedures

user defined functions

Lua

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Depending on the underlying data source

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

Depending on the underlying data source

yes

using MemoryDB

yes

using specific database classes

User concepts

Access control

Depending on the underlying data source

simple password-based access control and ACL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Apache Drill vs. Apache Spark — Which SQL query engine is better for you?
23 September 2019, Towards Data Science

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Drill Mines Diverse Data Sets, Google Style
20 May 2015, The Next Platform

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page