DBMS > BoltDB vs. Drizzle vs. EJDB vs. Oracle NoSQL

System Properties Comparison BoltDB vs. Drizzle vs. EJDB vs. Oracle NoSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

An embedded key-value store for Go.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Key-value store

Relational DBMS

Document store

Document store
Key-value store
Relational DBMS

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

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

github.com/boltdb/bolt

github.com/Softmotions/ejdb

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Drizzle project, originally started by Brian Aker

Softmotions

Oracle

Initial release

2013

2008

2012

2011

Current release

7.2.4, September 2012

23.3, December 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

GNU GPL

Open Source

GPLv2

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X

server-less

Linux
Solaris SPARC/x86

Data scheme

schema-free

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

optional

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

with proprietary extensions

SQL-like DML and DDL statements

APIs and other access methods

JDBC

in-process shared library

RESTful HTTP API

Supported programming languages

C
C++
Java
PHP

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

yes

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

off heap cache

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users and roles

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.com

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

provided by Google News

Enhance enterprise data security and trust: Must see Blockchain Technology sessions at Oracle CloudWorld 2023
21 August 2023, Oracle

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, Oracle

Oracle Beefs Up Its NoSQL Database Offering
3 April 2014, Data Center Knowledge

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

NoSQL Rebels Aim Missile at Larry Ellison's Yacht
20 July 2012, WIRED

provided by Google News

Share this page