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

Performance goals


It's time to switch gears and think about testing the performance of our Flux architecture. Testing the performance of a particular component can be difficult for the same reason that testing the functionality of a component is difficult—we have to isolate it from other code. On the other hand, our users don't necessarily care about the performance of individual components—just the overall user experience.

In this section, we'll discuss what we're trying to achieve with our Flux architecture in terms of performance. We'll start with the user perceived performance of the application, because this is the most consequential aspect of an under-performing architecture. Next, we'll think about measuring the raw performance of our Flux components. Finally, we'll consider the benefits of putting performance requirements in place for when we develop new components.

User perceived performance

From the point of view of our users, our application either feels responsive or laggy. This...