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

Development methodologies


In this section, we'll look at the development methodologies that take place at different stages of a Flux project. Keep in mind that these are just guidelines, as methodologies can vary quite drastically from team to team. If two different teams are implementing a Flux system, there will no doubt be some commonalities.

First we'll think about what happens during the initial phases of a new Flux project. Then we'll think about Flux projects that have had a chance to mature, and what the process might look like for adding a new feature to the system.

Upfront Flux activities

Many software development methodologies frown upon big upfront design. The reason is simple—we spend too much time designing before any software is written and tested. Incrementally delivering pieces of software gives us a chance to validate any assumptions we may have made while writing code. The question is, does Flux require big upfront design, or can we incrementally implement parts of a Flux...