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:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 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