Book Image

Flux Architecture

By : Adam Boduch
Book Image

Flux Architecture

By: Adam Boduch

Overview of this book

Whilst React has become Facebook’s poster-child for clean, complex, and modern web development, it has quietly been underpinned by its simplicity. It’s just a view. The real beauty in React is actually the architectural pattern that handles data in and out of React applications: Flux. With Flux, you’re able to build data-rich applications that engage your users, and scale to meet every demand. It is a key part of the Facebook technology stack that serves billions of users every day. This book will start by introducing the Flux pattern and help you get an understanding of what it is and how it works. After this, we’ll build real-world React applications that highlight the power and simplicity of Flux in action. Finally, we look at the landscape of Flux and explore the Alt and Redux libraries that make React and Flux developments easier. Filled with fully-worked examples and code-first explanations, by the end of the book, you'll not only have a rock solid understanding of the architecture, but will be ready to implement Flux architecture in anger.
Table of Contents (21 chapters)
Flux Architecture
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Profiling tools


The various profiling tools available to us through a web browser are often enough to address any performance issues in our interface. These include the components that make up our Flux architecture. In this section, we'll go over the three main tools found in browser developer tools that we'll want to use to profile our Flux architecture.

First are the action creator functions, specifically asynchronous functions. Then we'll think about the memory consumption of our Flux components. Finally, we'll discuss CPU utilization.

Asynchronous actions

The network is always going to be the slowest layer of the application. Even if the API call we're making is relatively fast, it's still slow compared to other JavaScript code. If our application didn't make any network requests, it would be blazing fast. It also wouldn't be of much use. Generally speaking, JavaScript applications rely on remote API endpoints as their data resources.

To make sure that these network calls aren't causing...