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 Redis vs MongoDB

Heroku Redis vs MongoDB

OverviewDecisionsComparisonAlternatives

Overview

MongoDB
MongoDB
Stacks96.6K
Followers82.0K
Votes4.1K
GitHub Stars27.7K
Forks5.7K
Heroku Redis
Heroku Redis
Stacks105
Followers163
Votes5

Heroku Redis vs MongoDB: What are the differences?

Introduction:

When it comes to choosing between Heroku Redis and MongoDB for your web application, there are key differences that you should consider before making a decision.

  1. Data Structure: Heroku Redis is an in-memory data structure store which can be used as a database, cache, and message broker. It is best suited for applications that require high read and write throughput, such as real-time analytics or caching. MongoDB, on the other hand, is a document-oriented database that stores data in JSON-like documents. It is designed for applications that require flexible schemas and complex data structures.

  2. Query Language: Heroku Redis does not support querying data based on values stored in the data structure. It is a key-value store, which means you can only retrieve data using keys. MongoDB, on the other hand, supports a rich query language that allows you to retrieve data based on specific criteria, such as values, ranges, or patterns.

  3. Scaling: Heroku Redis is designed to be highly scalable by allowing you to add more instances to your deployment to handle increased traffic. However, scaling with Heroku Redis can be costly as you pay for each additional instance. MongoDB, on the other hand, supports horizontal scaling by sharding your data across multiple servers. This allows you to handle increased load without incurring high costs.

  4. Data Persistence: Heroku Redis stores data in memory, which means data is lost when the server is restarted or fails. This makes it unsuitable for applications that require data persistence. MongoDB, on the other hand, stores data on disk by default, providing data persistence even in the event of a server failure or restart.

  5. Schema Flexibility: Heroku Redis does not enforce any schema on the data stored in the database, making it flexible for storing any type of data. MongoDB, on the other hand, allows you to define schemas for your data, providing structure and validation for your documents.

  6. Use Cases: Heroku Redis is best suited for applications that require high-performance data access and caching, such as real-time analytics, session storage, or message brokering. MongoDB, on the other hand, is ideal for applications that require flexible schemas, complex data structures, and rich querying capabilities, such as content management systems, e-commerce platforms, or social networking sites.

In Summary, when choosing between Heroku Redis and MongoDB, consider factors such as data structure, query language, scaling, data persistence, schema flexibility, and use cases to determine which solution best fits your 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, Heroku Redis

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

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 Redis is an in-memory key-value data store, run by Heroku, that is provisioned and managed as an add-on. Heroku Redis is accessible from any language with a Redis driver, including all languages and frameworks supported by Heroku.

Flexible data model, expressive query language, secondary indexes, replication, auto-sharding, in-place updates, aggregation, GridFS
Easily Optimize;Vertically Scalable
Statistics
GitHub Stars
27.7K
GitHub Stars
-
GitHub Forks
5.7K
GitHub Forks
-
Stacks
96.6K
Stacks
105
Followers
82.0K
Followers
163
Votes
4.1K
Votes
5
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
  • 5
    More reliable than the other Redis add-ons
Cons
  • 1
    More expensive than the other options
Integrations
No integrations available
Heroku
Heroku
Redis
Redis

What are some alternatives to MongoDB, Heroku Redis?

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