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:

Parsing PDFs in Node.js

Parsing PDFs in Node.js

This guide covers the top npm packages for parsing PDFs in Node.js, including pdf-parse, pdf2json, and pdfreader.

Chibuike Nwachukwu
Mar 4, 2024 ⋅ 7 min read
Implementing In App Updates For React Native Apps

Implementing in-app updates for React Native apps

Implementing OTA in-app updates in React Native apps can streamline the update process, preventing delays that hinder overall productivity.

Nelson Michael
Mar 1, 2024 ⋅ 7 min read
Exploring Stylex And The New Generation Of Styling Libraries

Exploring StyleX and the new generation of styling libraries

StyleX is a build-time, type-safe CSS-in-JS library recently open sourced by Meta. Explore StyleX and the evolution of styling libraries.

Ibadehin Mojeed
Feb 29, 2024 ⋅ 9 min read
Building High Performance Ecommerce Sites With Astro

Building high-performance ecommerce sites with Astro

Learn to set up a completely custom Astro ecommerce implementation that’s also highly performant and type-safe in this straightforward guide.

Onuorah Bonaventure
Feb 28, 2024 ⋅ 64 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