Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Flux Architecture
  • Table Of Contents Toc
Flux Architecture

Flux Architecture

By : Adam Boduch
3 (1)
close
close
Flux Architecture

Flux Architecture

3 (1)
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 (16 chapters)
close
close
15
Index

View responsibilities


At this point in the book, you probably have a pretty good handle on the role of view components in a Flux architecture. Put simply, their job is to display store information for users by inserting it into the DOM. In this section, we'll break this core view concept into three parts.

First there's the input to the views—the store data. Next, we have the structure of the view itself, and the various ways that it can be decomposed into smaller views. Finally, there's the user interactivity. Each of these three areas of view components has a relation to the flow of data through our Flux architecture. Let's look at each of them now.

Rendering store data

If the store transforms data into information that the user needs, then why have views at all? Why not have the stores directly render the information to the DOM? We need views for a couple reasons. First of all, a store could actually be used in several places, rendered by several views. Second of all, Flux isn't necessarily...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Flux Architecture
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon