Building Resilient Frontend Architecture

Explore frontend architecture resilience in this GOTO Berlin 2019 conference talk. Learn how to design application architectures that withstand change and defend against entropy in systems with frequent updates. Discover the meaning of architecture in frontend development, debunk common myths, and examine specific tools and techniques across micro to macro scales. Gain insights on avoiding the trap of constant rewrites, understanding technical debt, and the "Second System Effect." Delve into architecture as constraints, connected development, internal dependencies, and strategies for code reuse and decoupling. Master techniques like enforcing boundaries with forbidden dependency tests and using tools such as Dependency Cruiser. Conclude with valuable lessons on deriving architecture and maintaining system resilience in the face of inevitable change and legacy code.

Introduction
My First Job
Technical Debt
The Second System Effect
Why Rewrite Software
Architecture is a Dirty Word
Architecture as Constraints
Software as Constraints
Connected Development
Constraints
Internal Dependencies
Example
Shared Components
Code Reuse
Code Decoupled
Enforce Boundaries
Forbidden Dependency Tests
Dependency Cruiser
Recap
Dont derive architecture from first principles