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

Summary


The focus of scaling a Flux architecture is on the information that stores produce, rather than the various components. This chapter started with a discussion on the common practices of other architectures that involve the constant creation and destruction of JavaScript components. This is done to free resources, but it comes at a cost—the potential for error. Next, we looked at the relatively static nature of Flux architectures, where components have a long life. They don't have to constantly create and destroy components, which means that there's less potential for issues.

Next, we covered the concept of scaling information. We did so by demonstrating that our JavaScript components and the connections between them were the least of our worries when it comes to scaling the architecture. The real challenge comes when there's a lot of data to process, and the data that enters the system is likely to grow much faster than the number of JavaScript components we have.

We closed the chapter...