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


In this chapter, you learned about the action creator functions that Flux applications utilize in order to dispatch actions. Without action creator functions, we'd have to directly interface with the dispatcher in our code, which makes the architecture more difficult to reason about.

We started off by thinking about action naming conventions and the general organization of our action modules. Grouping action creators by feature has implications for modularity as well, especially in how this influences modularity in other areas of the architecture.

Next, we discussed mocking data using action creator functions. Mocking data in Flux applications is easy to do and encouraged. Actions are the only way for data to enter the system, making it easy for us to switch between mocked action data and our production implementations. We wrapped the chapter up with a look at stateful action creators that listen to things such as web socket connections, and a look at parameterized action creators...