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

The downsides of ReactJS


Now that you have a good handle on the benefits of using ReactJS as the view layer in a Flux architecture, it's time to look at some of the downsides. Everything has negative tradeoffs—there's no such thing as a perfect technology. So these things are worth considering in the context of a Flux architecture for your application.

First, we'll consider memory consumption. React is a fairly big library and has a noticeable impact on application load time. However, this is of minor concern compared to the amount of memory consumed by the virtual DOM. Next, we'll look at introducing JSX syntax into our JavaScript modules and the problems that might introduce for those not accustomed to blending other languages into their JavaScript modules.

Virtual DOM and memory

JavaScript applications should strive to be as memory-efficient as possible. Those that don't feel bloated and unresponsive to the user. Applications that use a lot of memory are inherently slower than those that...