DBMS > Atos Standard Common Repository vs. Firebolt vs. Google BigQuery vs. LevelDB vs. Microsoft Access

System Properties Comparison Atos Standard Common Repository vs. Firebolt vs. Google BigQuery vs. LevelDB vs. Microsoft Access

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

Large scale data warehouse service with append-only tables

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

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Relational DBMS

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

Score	1.73
Rank	#140	Overall
	#63	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.firebolt.io

cloud.google.com/bigquery

github.com/google/leveldb

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

Technical documentation

docs.firebolt.io

cloud.google.com/bigquery/docs

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

developer.microsoft.com/en-us/access

Developer

Atos Convergence Creators

Firebolt Analytics Inc.

Google

Microsoft

Initial release

2016

2020

2010

2011

1992

Current release

1703

1.23, February 2021

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Bundled with Microsoft Office

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

hosted

Illumos
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

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

APIs and other access methods

LDAP

.Net
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages with LDAP bindings

Go
JavaScript (Node.js)
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

Since BigQuery is designed for querying data

ACID

but no files for transaction logging

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

In-memory capabilities

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

yes

User concepts

Access control

LDAP bind authentication

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

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.