Flexible data flow architecture in Angular
summary
Summarizes concrete Angular techniques: uses no external state libraries, enumerates component-level bindings, Inputs/Outputs and ViewChild, services, router data, injection tokens, and browser storage, and shows a real project using localStorage to pass settings between apps. Names four design patterns (lists four design patterns — mediator bridge singleton chain of responsibility) and contrasts smart vs dumb components with tradeoffs. Recommends lifecycle hooks, resolvers or app initializer for timing and lazy loading choices, and notes interceptors and template sync as automated options.
AI-written summary · about
chapters (9)
- 0:00Intro
- 3:11STAIRS, WINDOWS, CORRIDORS, ELEVATORS
- 4:18HOW DATA FLOW WITHIN ONE COMPONENT
- 5:47HOW DATA FLOW WITHIN NESTED COMPONENTS
- 8:51HOW DATA FLOW BETWEEN APPS
- 10:07HOW DOES DATA GET INTO YOUR COMPONENT
- 11:11DESIGN PATTERNS DATA PERSPECTIVE
- 13:38WHERE: AUTONOMY AND FLEXIBILITY
- 15:49WHEN DO YOU GET YOUR DATA?
related talks
44mData Flow Patterns in Angular 2
26mSoftware Patterns and Design with AngularJS
27mAngular Architecture: From Patterns to Implementation
30mAngular: Keeping it Fat, Dumb, and Happy: An Architectural Approach
32mAngular2 Data Flow
24mDay 2 Keynote, Angular Architecture Concepts and Practices
18mLightweight Architectures with Angular's Latest Innovations
26mScalable Angular Architecture