2021-05-28
3651
#react
Varun Pujari
51372
May 28, 2021 â‹… 13 min read

Using MobX for large-scale enterprise state management

Varun Pujari Software Engineer | IoT Geek | Always ready for a game of chess

Recent posts:

SOLID Series: Liskov Substitution Principle (LSP)

A deep dive into the Liskov Substitution Principle with examples, violations, and practical tips for writing scalable, bug-free object-oriented code.

Oyinkansola Awosan
Jun 6, 2025 â‹… 10 min read
Modern CSS Carousels: No JavaScript Required

Modern CSS carousels: No JavaScript required

This article walks through new CSS features like ::scroll-button() and ::scroll-marker() that make it possible to build fully functional CSS-only carousels.

Saleh Mubashar
Jun 6, 2025 â‹… 5 min read
hidden coast of developer elitism

It’s time to break the cycle of developer elitism

Let’s talk about one of the greatest problems in software development: nascent developers bouncing off grouchy superiors into the arms of AI.

Lewis Cianci
Jun 4, 2025 â‹… 9 min read
When To Use Flexbox And When To Use CSS Grid

When to use Flexbox and when to use CSS Grid

Flexbox and Grid are the heart of modern CSS layouts. Learn when to use each and how they help build flexible, responsive web designs — no more hacks or guesswork.

Leonardo Maldonado
Jun 3, 2025 â‹… 9 min read
View all posts

4 Replies to "Using MobX for large-scale enterprise state management"

  1. This is amazing tutorial.
    Thank you so much!

    Unfortunately, I didn’t get the main point of using MobX in this exact tutorial. I know it is a tutorial about using MobX but I would like to see the benefits of using MobX here, please.

  2. Thank you. I like idea with private store inside other stores!

    Also, to ANJD, I didn’t get the main point of using Redux from your reply, I would like to see the benefits of using Redux here, please.

  3. What bothers me about this project is this process:
    – The view calls posts and comments APIs
    – APIs fill stores
    – The model refers to stores
    – The view gets the model
    Therefore the view handle the logic of domain services. But this is not its role to know that the comments API have to be called to construct the post model.
    So i think a layer – like a Controller or a ViewModel – is missing to separate the presentation to the logic.

  4. Sorry I didn’t get the point that why we need to keep the Context layer? Can’t we just export/import the store and api directly?

Leave a Reply