Introduction to the newline guide to building a React App with MobX State Tree

Application Overview

State Management on the JavaScript ecosystem

State Management

What is MobX State Tree?

What will you learn in this course?

Will this course be for you?

Introduction

Introduction to the mental model of MobX State Tree

The Tree in MobX State Tree

Introduction to the store model of MobX State Tree

The Store Model

Introduction to the types in MobX State Tree

Types

Introduction to the model actions of MobX State Tree

Model Actions

Introduction to the model views of MobX State Tree

Model Views

Introduction to the store snapshots of MobX State Tree

Snapshots

Identifiers and references of MobX State Tree

Identifiers and References

Asynchronous Actions

Lifecycle Hooks

Concepts

Arrays in MobX State Tree

Maps

Working with nested stores in MobX State Tree

Nesting Stores

Optimistic Updates

Time Travel

Advanced Concepts

Overview of React and MobX State Tree

Combining MobX State Tree with React via Context and a custom Hook

Context and Hooks

Observable

React

Overview

Building Voyager

mobx-state-tree

In this course, we will create a complete React Application with the state management handled by MobX State Tree, a state container system that is built on MobX, a functional reactive state library.

MobX State Tree will give your application a solid structure and foundation for large-scale applications and for small applications that are expected to scale rapidly. In comparison to Redux, MobX State Tree outstands it in performance with much less boilerplate. MobX is one of the most popular Redux alternatives and it's used by companies all over the world, including Netflix, Grow, IBM, DAZN, Baidu, and more.

During this course, you'll learn:

* Types in MobX State Tree.
* How to create the architecture of a centralized store.
* How to mutate the state via actions that could be asynchronous or not, depending on if we need to perform network requests to persist data into a database via GraphQL.
* Understanding snapshots and how we can benefit from them to time-travel if a network request fails.
* Understanding how MobX State Tree makes use of observable properties and observers.
* Leveraging re-renders in your React Application to MobX observers for better performance optimizations.

By the end of this course, you will have the knowledge and skills that it takes to build a real-world, production-level React Application with a State Management with top-notch performance that can scale with ease.

In this course, we'll show you how to build a React App with MobX State Tree.

The newline Guide to Building a React App with MobX State Tree

How to integrate MobX State Tree within your React App

Dealing with asynchronous flows and time travel to preserve state on networking errors

How to create a scalable store using MobX State Tree

---
title: The Tree in MobX State Tree
slug: the-tree-in-mobx-state-tree
description: Introduction to the mental model of MobX State Tree
role: "LESSON"
isPublicLesson: false
---

# The Tree in MobX State Tree

When you think about MobX State Tree, you have to think of something similar to a tree, that grows from one entry point (the roots of the tree) into many branches having many leaves that contain your data.

![Mental model of a MobX State Tree store](https://d2uusema5elisf.cloudfront.net/courses/newline-guide-to-building-a-react-app-with-mobx-state-tree/module_01/lesson_01.01/public/concept-of-store.jpg)

As we can see by the schema above, we have a root node with two branch nodes and each one of these branch nodes have two other leaf nodes. This is the graph-like architecture that was mentioned in the introduction of this course and this is how all of your stores in MobX State Tree will be structured.

A node can have as many child nodes as you want to, but remember that with each node that you add, the complexity of the store will increase, and even though MST will handle all of the node structures and dependencies, you might end up losing yourself in a huge node tree. We should always keep things as simple as possible and well organized so we don't end up with a ton of files trying to figure out where something is.
