If you landed in this section, you might be wondering at this point, "what should I do now?". Here is where we provide some essential tips/suggestions on how to diverge from creating trivial TodoMVC apps to a real world application.

Tips & Considerations For The Real World

Whenever we decide to create a new project, we tend to bypass several aspects that in the future may slow us down. In a real world project we have to consider several things before we start coding, such as: how to configure a store, store size, data structure, state model, middlewares, environment, async transactions, immutability and etc..

Those above are some of the main considerations we have to think beforehand. It's not an easy task but there are some strategies on how to go through it smoothly.

UI vs State

One of the biggest challenges developers face when using Redux is to describe UI state with data. The majority software programs out there are just data transformation and having the clear understanding that UI's are simply data beautifully presented facilitates the process of building it.

Nicolas Hery describes it really well in "Describing UI state with data". Also, it's always good to know When to use Redux, because a lot of times You Might Not Need Redux

Configure a Store

To configure a store we have to make major considerations on which middleware to use. There are several libraries out there, but the most popular ones are:

Perform Asynchronous dispatch

  • redux-thunk

    • Redux Thunk middleware allows you to write action creators that return a function instead of an action. The thunk can be used to delay the dispatch of an action, or to dispatch only if a certain condition is met. It incorporates the methods dispatch and getState as parameters.

  • redux-saga

    • redux-saga is a library that aims to make application side effects (i.e. asynchronous like data fetching and impure procedures such as accessing the browser cache) in a manageable and efficient way to execute. It's simple to test as it uses the ES6 feature called generators, making the flow easy to read as synchronous code.

  • redux-observable

    • redux-observable is a middleware for redux that is inspired by redux-thunk. It allows developers to dispatch a function that returns an Observable, Promise or iterable of action(s). When the observable emits an action, or the promise resolves an action, or the iterable gives an action out, that action is then dispatched as usual.

Development Purposes / debug

  • redux-devtools

    • Redux DevTools is a set of tools for your Redux development workflow.

  • redux-logger

    • redux-logger logs all actions that are being dispatched to the store.

To be able to choose one of these libraries we must take into account whether we are building a small or large application. Usability, code standards, and JavaScript knowledge may also be considered. All of them are similar.

Tip: Think of middlewares as skills you give to your store. i.e: By attributing the redux-thunk to your store, you're giving the store the ability to dispatch async actions.

Naming Convention

A big source of confusion when it comes to a large project is what to name things. This is often just as important as the code itself. Defining a naming convention for your actions at the very beginning of a project and sticking to that convention helps you to scale up as the scope of the project grows.

Great source: A Simple Naming Convention for Action Creators in Redux and Redux Patterns and Anti-Patterns

Tip: Set up an opinionated code formatter, such as Prettier.

Scalability

There is no magic to analyze and predict how much your application is going to grow. But it's okay! Redux's simplistic foundation means it will adapt to many kinds of applications as they grow. Here are some resources on how to build up your application in a sensible manner:

Tip: It's great to plan things beforehand, but don't get caught up in "analysis paralysis". Done is always better than perfect, after all. And Redux makes refactoring easy if you need to.

With all that being said, the best practice is to keep coding and learning. Participate in issues and StackOverFlow questions. Helping others is a great way of mastering Redux.

Tip: A respository with an extensive amount of content about best practices and Redux architecture shared by @markerikson at react-redux-links.