StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. Google Cloud Datastore vs MongoDB

Google Cloud Datastore vs MongoDB

OverviewDecisionsComparisonAlternatives

Overview

MongoDB
MongoDB
Stacks96.6K
Followers82.0K
Votes4.1K
GitHub Stars27.7K
Forks5.7K
Google Cloud Datastore
Google Cloud Datastore
Stacks290
Followers357
Votes12

Google Cloud Datastore vs MongoDB: What are the differences?

Introduction

Google Cloud Datastore and MongoDB are both popular NoSQL databases used for storing and managing large amounts of data. While they share some similarities, there are also key differences that set them apart. In this article, we will explore these differences in detail.

  1. Data model: The data model in Google Cloud Datastore is based on entities and properties, where an entity can have multiple properties. Each property can have a different data type. On the other hand, MongoDB uses a flexible and schema-less document model, where data is stored in JSON-like documents with dynamic schemas. This allows for more flexibility in data modeling and eliminates the need for predefined schemas in MongoDB.

  2. Querying: Google Cloud Datastore offers a powerful query language called GQL (Google Query Language), which allows you to perform complex queries and filtering operations on entities and properties. MongoDB, on the other hand, uses a flexible and expressive query language that supports a rich set of operations like filtering, projection, sorting, and aggregation. MongoDB's query language provides more flexibility and control over the retrieval of data compared to Google Cloud Datastore.

  3. Scalability: Both Google Cloud Datastore and MongoDB are designed to scale horizontally and handle large amounts of data. However, they use different mechanisms for scaling. Google Cloud Datastore is a managed service provided by Google, which automatically handles scalability, replication, and load balancing. MongoDB, on the other hand, requires manual configuration and management of sharding to achieve horizontal scalability. This means that scaling up Google Cloud Datastore is easier and less time-consuming compared to MongoDB.

  4. Transactions: Google Cloud Datastore provides ACID (Atomicity, Consistency, Isolation, Durability) transactions, which guarantee data consistency and integrity. Transactions in Google Cloud Datastore are strongly consistent within entity groups, ensuring that all changes are visible atomically. MongoDB, on the other hand, has limited support for multi-document transactions. Transactions in MongoDB are implemented at the document level and do not have the same level of consistency guarantees as Google Cloud Datastore.

  5. Indexing: Indexing is crucial for performance in database systems. Google Cloud Datastore automatically builds indexes for all properties, allowing for efficient querying and retrieval of data. However, it does not support custom indexing strategies. MongoDB, on the other hand, allows for the creation of custom indexes, providing more control over query optimization and performance tuning. This makes MongoDB a better choice for applications with specific indexing requirements.

  6. Deployment options: Google Cloud Datastore is a fully managed service provided by Google, which means that it is hosted and maintained by Google and does not require any configuration or management on the user's part. MongoDB, on the other hand, can be deployed in various ways, including on-premises, in the cloud, or as a managed service like MongoDB Atlas. MongoDB provides more deployment flexibility compared to Google Cloud Datastore.

In summary, key differences between Google Cloud Datastore and MongoDB include their data models, querying capabilities, scalability mechanisms, transaction support, indexing options, and deployment choices. These differences make them suited for different use cases and application requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on MongoDB, Google Cloud Datastore

George
George

Student

Mar 18, 2020

Needs adviceonPostgreSQLPostgreSQLPythonPythonDjangoDjango

Hello everyone,

Well, I want to build a large-scale project, but I do not know which ORDBMS to choose. The app should handle real-time operations, not chatting, but things like future scheduling or reminders. It should be also really secure, fast and easy to use. And last but not least, should I use them both. I mean PostgreSQL with Python / Django and MongoDB with Node.js? Or would it be better to use PostgreSQL with Node.js?

*The project is going to use React for the front-end and GraphQL is going to be used for the API.

Thank you all. Any answer or advice would be really helpful!

620k views620k
Comments
Ido
Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k
Comments
Mike
Mike

Mar 20, 2020

Needs advice

We Have thousands of .pdf docs generated from the same form but with lots of variability. We need to extract data from open text and more important - from tables inside the docs. The output of Couchbase/Mongo will be one row per document for backend processing. ADOBE renders the tables in an unusable form.

241k views241k
Comments

Detailed Comparison

MongoDB
MongoDB
Google Cloud Datastore
Google Cloud Datastore

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

Use a managed, NoSQL, schemaless database for storing non-relational data. Cloud Datastore automatically scales as you need it and supports transactions as well as robust, SQL-like queries.

Flexible data model, expressive query language, secondary indexes, replication, auto-sharding, in-place updates, aggregation, GridFS
Schemaless access, with SQL-like querying;Managed database;Autoscale with your users;ACID transactions;Built-in redundancy;Local development tools
Statistics
GitHub Stars
27.7K
GitHub Stars
-
GitHub Forks
5.7K
GitHub Forks
-
Stacks
96.6K
Stacks
290
Followers
82.0K
Followers
357
Votes
4.1K
Votes
12
Pros & Cons
Pros
  • 829
    Document-oriented storage
  • 594
    No sql
  • 554
    Ease of use
  • 465
    Fast
  • 410
    High performance
Cons
  • 6
    Very slowly for connected models that require joins
  • 3
    Not acid compliant
  • 2
    Proprietary query language
Pros
  • 7
    High scalability
  • 2
    Ability to query any property
  • 2
    Serverless
  • 1
    Pay for what you use

What are some alternatives to MongoDB, Google Cloud Datastore?

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

Amazon DynamoDB

Amazon DynamoDB

With it , you can offload the administrative burden of operating and scaling a highly available distributed database cluster, while paying a low price for only what you use.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase