DBMS > BoltDB vs. Coveo vs. Databricks vs. HBase vs. RocksDB

System Properties Comparison BoltDB vs. Coveo vs. Databricks vs. HBase vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Primary database model

Key-value store

Search engine

Document store
Relational DBMS

Wide column store

Key-value store

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

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

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

Website

github.com/boltdb/bolt

Technical documentation

docs.coveo.com

docs.databricks.com

hbase.apache.org/book.html

github.com/facebook/rocksdb/wiki

Developer

Coveo

Databricks

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Facebook, Inc.

Initial release

2013

2012

2013

2008

2013

Current release

2.3.4, January 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache version 2

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

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux
Unix
Windows

using Cygwin

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

Flexible Schema (defined schema, partial schema, schema free)

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

SQL

Support of SQL

with Databricks SQL

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

Python
R
Scala

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Single row ACID (across millions of columns)

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

granular access controls, API key management, content filters

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.