DBMS > Amazon DocumentDB vs. Atos Standard Common Repository vs. Dolt vs. Google BigQuery

System Properties Comparison Amazon DocumentDB vs. Atos Standard Common Repository vs. Dolt vs. Google BigQuery

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Large scale data warehouse service with append-only tables

Primary database model

Document store

Document store
Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

aws.amazon.com/documentdb

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

github.com/dolthub/dolt
www.dolthub.com

cloud.google.com/bigquery

Technical documentation

aws.amazon.com/documentdb/resources

docs.dolthub.com

cloud.google.com/bigquery/docs

Developer

Atos Convergence Creators

DoltHub Inc

Google

Initial release

2019

2016

2018

2010

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

Server operating systems

hosted

Linux

Linux
macOS
Windows

hosted

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

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

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

LDAP

CLI Client
HTTP REST

RESTful HTTP/JSON API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages with LDAP bindings

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

Atomic execution of specific operations

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

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

Access rights for users and roles

LDAP bind authentication

Only one user is configurable, and must be specified in the config file at startup

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

Google Cloud Identity & Access Management (IAM)

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.