DBMS > Badger vs. BoltDB vs. Coveo vs. Lovefield vs. RocksDB

System Properties Comparison Badger vs. BoltDB vs. Coveo vs. Lovefield vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Embeddable relational database for web apps written in pure JavaScript

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

github.com/dgraph-io/badger

github.com/boltdb/bolt

www.coveo.com

google.github.io/lovefield

rocksdb.org

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.coveo.com

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

github.com/facebook/rocksdb/wiki

Developer

DGraph Labs

Coveo

Google

Facebook, Inc.

Initial release

2017

2013

2012

2014

2013

Current release

2.1.12, February 2017

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MIT License

commercial

Open Source

Apache 2.0

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

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

tested with Chrome, Firefox, IE, Safari

Linux

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

RESTful HTTP API

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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.

yes

using MemoryDB

yes

User concepts

Access control

granular access controls, API key management, content filters

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.