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

Abstract dispatcher interface


The idea with any reference implementation is to directly illustrate, using code, how something is supposed to work. The Facebook reference implementation of the Flux dispatcher does just that—we can use it in a real Flux architecture and get results. We also gain an understating of the abstract dispatcher interface. Put another way, the reference implementation is kind of like software requirements, expressed in code form.

In this section, we'll try to better understand what these minimum requirements are before we dive into our own dispatcher implementation. The first essential piece of functionality that the dispatcher must implement is store registration so that the dispatcher can dispatch payloads to it. Then, we need the actual dispatching mechanism, which iterates over the registered stores and delivers payloads. Finally, we have the dependency semantics to think about while we're dispatching payloads.

Store registration

When we instantiate a store, we have...