Sacrificial Architecture in modern web development
summary
Claims that designing code to be disposable — sacrificial architecture — makes frontends easier to rewrite, demonstrates concrete tactics: split into isolated modules, accept deliberate duplication, keep shared surface minimal, and prefer ES6 modules and fetch so business logic is framework‑free. Shows replacing Angular 1 with React with little effort and using an event bus (Redux Flux MobX RxJS) to decouple view and logic. Result: parts get rewritten independently and the app keeps running.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:41What's the main purpose of Agile?
- 1:12Embrace Change
- 1:36Describe your average Software Architecture
- 3:55Introducing Sacrificial Architecture
- 5:10The whole project
- 6:17Incremental
- 7:58Sacrificial Web Development
- 8:16Modularity
- 11:09Frameworks
- 13:43Design your way out of a framework
- 15:31UI Components are Microservices for frontend development
- 16:02Separate Logic
related talks
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
49mFrom Frameworks to Superframeworks
18mSoftware Architecture Building Better Applications with Architecture Best Practices
22mHow to make robust and scalable front-end using layers
34mScalable Angular Architecture
28mRequiem for APIs - The Evolution of Web Development
30mThe age of hooks Framework agnostic frontends might be surprisingly powerful
36mKeep it simple! How to apply KISS principle in modern frontend