DBMS > BoltDB vs. Linter vs. RocksDB vs. searchxml vs. Vitess

System Properties Comparison BoltDB vs. Linter vs. RocksDB vs. searchxml vs. Vitess

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

RDBMS for high security requirements

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

DBMS for structured and unstructured content wrapped with an application server

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store

Relational DBMS

Key-value store

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial 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.09
Rank	#346	Overall
	#152	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/boltdb/bolt

linter.ru

rocksdb.org

www.searchxml.net/category/products

vitess.io

Technical documentation

github.com/facebook/rocksdb/wiki

www.searchxml.net/support/handouts

vitess.io/docs

Developer

relex.ru

Facebook, Inc.

informationpartners gmbh

The Linux Foundation, PlanetScale

Initial release

2013

1990

2013

2015

2013

Current release

8.11.4, April 2024

1.0

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

BSD

commercial

Open Source

Apache Version 2.0, commercial licenses available

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 and C++

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

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

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

C++ API
Java API

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Go
Java
Perl
Python
Ruby

C++

most other programming languages supported via APIs

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

on the application server

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

sychronisation to multiple collections

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

yes

multiple readers, single writer

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept

no user groups or 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.