DBMS > BoltDB vs. MarkLogic vs. RocksDB vs. Snowflake vs. SwayDB

System Properties Comparison BoltDB vs. MarkLogic vs. RocksDB vs. Snowflake vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Operational and transactional Enterprise NoSQL database

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

Cloud-based data warehousing service for structured and semi-structured data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Relational DBMS

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	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

github.com/boltdb/bolt

Technical documentation

docs.marklogic.com

github.com/facebook/rocksdb/wiki

docs.snowflake.net/manuals/index.html

Developer

MarkLogic Corp.

Facebook, Inc.

Snowflake Computing Inc.

Simer Plaha

Initial release

2013

2001

2013

2014

2018

Current release

11.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

BSD

commercial

Open Source

GNU Affero GPL V3.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++

Scala

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux

hosted

Data scheme

schema-free

Schema can be enforced

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

C++ API
Java API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

JavaScript (Node.js)
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

yes

ACID

Atomic execution of operations

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, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept, user roles and pluggable authentication

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.