What is MobX?
MobX is a battle tested library that makes state management simple and scalable by transparently applying functional reactive programming (TFRP). React and MobX together are a powerful combination. React renders the application state by providing mechanisms to translate it into a tree of renderable components. MobX provides the mechanism to store and update the application state that React then uses.
MobX is a tool in the State Management Library category of a tech stack.
MobX is an open source tool with 26.5K GitHub stars and 1.8K GitHub forks. Here’s a link to MobX's open source repository on GitHub
Who uses MobX?
130 companies reportedly use MobX in their tech stacks, including Udemy, Canva, and Frontend Stack.
437 developers on StackShare have stated that they use MobX.
Pros of MobX
It's just stupidly simple, yet so magical
Easier and cleaner than Redux
ES6 observers and obversables
Flexible architecture the requeriment
Has own router package (mobx-router)
Decisions about MobX
Here are some stack decisions, common use cases and reviews by companies and developers who chose MobX in their tech stack.
I am building a POC in Next.js. I usually use CRA+ MobX + Contentful, but this time I want to give a try to Next and GraphQL. Any suggestions on what tool to use for state management/content management? I am looking for a modern and quick to implement solution.
Jun 14 2018 at 2:23AM
MobX Alternatives & Comparisons
What are some alternatives to MobX?
See all alternatives
Never again communicate with your data store using an imperative API. Simply declare your data requirements using GraphQL and let Relay figure out how and when to fetch your data.
A custom middleware for graphql-ruby that handles key construction and cache reads/writes transparently.
Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.
Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.