DBMS > LevelDB vs. Microsoft Access vs. Snowflake vs. VoltDB

System Properties Comparison LevelDB vs. Microsoft Access vs. Snowflake vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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.)

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Relational DBMS

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

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/google/leveldb

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

www.snowflake.com

www.voltdb.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Google

Microsoft

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2011

1992

2014

2010

Current release

1.23, February 2021

1902 (16.0.11328.20222), March 2019

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD

commercial

Bundled with Microsoft Office

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Server operating systems

Illumos
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X

for development

Data scheme

schema-free

yes

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

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

but not compliant to any SQL standard

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Java

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

but no files for transaction logging

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

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

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

Users and roles with access to stored procedures

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.