DBMS > BoltDB vs. Microsoft Access vs. RocksDB vs. ScyllaDB

System Properties Comparison BoltDB vs. Microsoft Access vs. RocksDB vs. ScyllaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Cassandra and DynamoDB compatible wide column store

Primary database model

Secondary database models

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	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Website

github.com/boltdb/bolt

www.microsoft.com/en-us/microsoft-365/access

rocksdb.org

www.scylladb.com

Technical documentation

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

docs.scylladb.com

Developer

Microsoft

Facebook, Inc.

ScyllaDB

Initial release

2013

1992

2013

2015

Current release

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Bundled with Microsoft Office

Open Source

BSD

Open Source

Open Source (AGPL), commercial license 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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

Linux

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.

Secondary indexes

yes

cluster global secondary indices

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements (CQL)

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Supported programming languages

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C
C++
Go
Java
Perl
Python
Ruby

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes, Lua

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

Representation of geographical distribution of servers is possible

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

but no files for transaction logging

yes

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

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

yes

in-memory tables

User concepts

Access control

a simple user-level security was built in till version Access 2003

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» 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.