DBMS > Google Cloud Datastore vs. LevelDB vs. Microsoft Access vs. MongoDB vs. ToroDB

System Properties Comparison Google Cloud Datastore vs. LevelDB vs. Microsoft Access vs. MongoDB vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

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

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	2.75
Rank	#107	Overall
	#19	Key-value stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	423.96
Rank	#5	Overall
	#1	Document stores

Website

cloud.google.com/datastore

github.com/google/leveldb

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

www.mongodb.com

github.com/torodb/server

Technical documentation

cloud.google.com/datastore/docs

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

developer.microsoft.com/en-us/access

www.mongodb.com/docs/manual

Developer

Google

Microsoft

MongoDB, Inc

8Kdata

Initial release

2008

2011

1992

2009

2016

Current release

1.23, February 2021

1902 (16.0.11328.20222), March 2019

6.0.7, June 2023

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Bundled with Microsoft Office

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

yes

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

MongoDB Atlas: Global multi-cloud database with unmatched data distribution and mobility across AWS, Azure, and Google Cloud, built-in automation for resource and workload optimization, and so much more.

Implementation language

C++

Java

Server operating systems

hosted

Illumos
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

Read-only SQL queries via the MongoDB Atlas SQL Interface

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
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

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Server-side scripts

Stored procedures

using Google App Engine

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

since Access 2010 using the ACE-engine

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

but no files for transaction logging

Multi-document ACID Transactions with snapshot isolation

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

optional, enabled by default

yes

In-memory capabilities

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

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

MongoDB provides an integrated suite of cloud database and data services to accelerate...
» more

Competitive advantages

Built around the flexible document data model and unified API, MongoDB is a developer...
» more

Typical application scenarios

AI-enriched intelligent apps (Continental, Telefonica, Iron Mountain) Internet of...
» more

Key customers

ADP, Adobe, Amadeus, AstraZeneca, Auto Trader, Barclays, BBVA, Bosch, Cisco, CERN,...
» more

Market metrics

Hundreds of millions downloads, over 150,000+ Atlas clusters provisioned every month...
» more

Licensing and pricing models

MongoDB database server: Server-Side Public License (SSPL) . Commercial licenses...
» 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.