DBMS > Blueflood vs. LevelDB vs. Microsoft Access vs. Snowflake vs. Valentina Server

System Properties Comparison Blueflood vs. LevelDB vs. Microsoft Access vs. Snowflake vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Object-relational database and reports server

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

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	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

blueflood.io

github.com/google/leveldb

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

www.snowflake.com

www.valentina-db.net

Technical documentation

github.com/rax-maas/blueflood/wiki

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

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Rackspace

Google

Microsoft

Snowflake Computing Inc.

Paradigma Software

Initial release

2013

2011

1992

2014

1999

Current release

1.23, February 2021

1902 (16.0.11328.20222), March 2019

5.7.5

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

commercial

Bundled with Microsoft Office

commercial

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

Java

C++

Server operating systems

Linux
OS X

Illumos
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Windows

Data scheme

predefined 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

APIs and other access methods

HTTP REST

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

ODBC

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

yes

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

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

fine grained access rights according to SQL-standard

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.