Главная
Study mode:
on
1
Introduction
2
My First Job
3
Technical Debt
4
The Second System Effect
5
Why Rewrite Software
6
Architecture is a Dirty Word
7
Architecture as Constraints
8
Software as Constraints
9
Connected Development
10
Constraints
11
Internal Dependencies
12
Example
13
Shared Components
14
Code Reuse
15
Code Decoupled
16
Enforce Boundaries
17
Forbidden Dependency Tests
18
Dependency Cruiser
19
Recap
20
Dont derive architecture from first principles
Description:
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.

Building Resilient Frontend Architecture

GOTO Conferences
Add to list
0:00 / 0:00