DBMS > BoltDB vs. Microsoft Azure AI Search vs. Oracle Berkeley DB vs. RocksDB vs. Warp 10

System Properties Comparison BoltDB vs. Microsoft Azure AI Search vs. Oracle Berkeley DB vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Search-as-a-service for web and mobile app development

Widely used in-process key-value store

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Key-value store

Search engine

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Time Series DBMS

Secondary database models

Vector DBMS

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

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

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

github.com/boltdb/bolt

azure.microsoft.com/en-us/services/search

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

www.warp10.io

Technical documentation

learn.microsoft.com/en-us/azure/search

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

SenX

Initial release

2013

2015

1994

2013

2015

Current release

18.1.40, May 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

commercial license available

Open Source

BSD

Open Source

Apache License 2.0

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

C, Java, C++ (depending on the Berkeley DB edition)

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP API

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
Java
JavaScript
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Source-replica replication

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

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

In-memory capabilities

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

yes

User concepts

Access control

yes

using Azure authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.