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. Heroku Postgres vs MongoDB

Heroku Postgres vs MongoDB

OverviewDecisionsComparisonAlternatives

Overview

MongoDB
MongoDB
Stacks96.6K
Followers82.0K
Votes4.1K
GitHub Stars27.7K
Forks5.7K
Heroku Postgres
Heroku Postgres
Stacks607
Followers314
Votes38

Heroku Postgres vs MongoDB: What are the differences?

Introduction

In the world of web development, database management systems play a crucial role in storing, retrieving, and managing data efficiently. Two popular options for this purpose are Heroku Postgres and MongoDB. While both serve as reliable solutions, there are several key differences between them that developers should consider before making a choice.

  1. Data Structure: Heroku Postgres is a relational database management system (RDBMS) that organizes data in tables with predefined schemas, offering a structured approach to data storage. In contrast, MongoDB is a NoSQL database that stores data in flexible, JSON-like documents without strict schemas, allowing for easy scalability and adaptability.

  2. Query Language: Heroku Postgres uses Structured Query Language (SQL) as its query language, which provides a standardized and well-defined syntax for accessing and manipulating data. On the other hand, MongoDB uses its own query language that supports document-based queries, making it more suitable for handling unstructured or complex data.

  3. Scalability and Performance: Heroku Postgres excels in handling complex joins and transactions, making it a go-to choice for applications with complex relationships among data. It also offers features like indexing and query optimization for efficient performance. In contrast, MongoDB is designed to scale horizontally and can handle large amounts of data with ease. It provides sharding and replication capabilities to distribute data across multiple servers, ensuring high availability and performance in large-scale applications.

  4. Data Integrity and Constraints: Heroku Postgres enforces strict data integrity constraints through its support for ACID (Atomic, Consistent, Isolated, Durable) transactions, making it suitable for applications where data consistency is critical. MongoDB, being a NoSQL database, is more flexible in terms of data integrity and allows developers to choose trade-offs between consistency, availability, and partition tolerance, emphasizing flexibility over strict consistency.

  5. Schema Evolution: With Heroku Postgres, adding, modifying, or deleting columns in a table requires careful consideration as it affects the entire database structure. Any changes in the schema may impact existing functionality, and migrations need to be handled properly. In contrast, MongoDB's schema-less nature allows for easy schema evolution, where developers can add or remove fields from documents without affecting other parts of the database, simplifying the development process.

  6. Community and Ecosystem: Heroku Postgres has been in the market for a long time and has a well-established community. It offers various tools, libraries, and frameworks that integrate seamlessly with the PostgreSQL ecosystem, providing extensive support for different programming languages. MongoDB also has a strong and growing community, with an active ecosystem of tools and libraries. It is particularly popular in the JavaScript and Node.js community, offering native support and integrations for these technologies.

In summary, the key differences between Heroku Postgres and MongoDB lie in their data structuring, query languages, scalability and performance capabilities, data integrity models, schema evolution approaches, and community ecosystems. Choosing the right database depends on the specific requirements of the application, considering factors like the nature of data, relationships, scalability needs, and development preferences.

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, Heroku Postgres

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
Heroku Postgres
Heroku Postgres

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.

Heroku Postgres provides a SQL database-as-a-service that lets you focus on building your application instead of messing around with database management.

Flexible data model, expressive query language, secondary indexes, replication, auto-sharding, in-place updates, aggregation, GridFS
High Availability;Rollback;Dataclips;Automated Health Checks
Statistics
GitHub Stars
27.7K
GitHub Stars
-
GitHub Forks
5.7K
GitHub Forks
-
Stacks
96.6K
Stacks
607
Followers
82.0K
Followers
314
Votes
4.1K
Votes
38
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
  • 29
    Easy to setup
  • 3
    Extremely reliable
  • 3
    Follower databases
  • 3
    Dataclips for sharing queries
Cons
  • 2
    Super expensive
Integrations
No integrations available
PostgreSQL
PostgreSQL
Heroku
Heroku

What are some alternatives to MongoDB, Heroku Postgres?

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.

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.

InfluxDB

InfluxDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

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