Observer Driven Design
summary
Argues that using the Observer applications view as a source of truth makes OTP design verifiable: builds a small app that synchronously validates and persists users then spawns email and analytics jobs, implements supervisors and workers (uses Tasks under supervisors and discusses ETS for state), shows the live supervision tree in Observer and how restarts, links, timing and proximity behave, reports it takes iterations to match diagram to runtime and that the Observer visibly confirms the design.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:16Observer Driven Design Omid Bachari
- 3:27What is the Observer?
- 5:43What is OTP?
- 6:14Scalability.
- 7:17Let's do OTP well.
- 9:31Example Application
- 10:45How should we implement?
- 14:22What are important things to illustrate?
- 15:49How does it look in the Observer?
- 17:07Other things we need to illustrate?
- 19:52Virtuous Cycle
related talks
01h 02mThe Observer Design Pattern in Cpp
33mThe Observer tip-jar
01h 20mRevisiting C++ Observers: Spooky Action at a Distance
01h 03mSpooky Action at a Distance
24mThe Dangers of Object-Oriented Designs
50mDomain Prototyping or Design Is How It Works
38mClients in control: building demand-driven systems with Om Next
38mErlang Patterns, Open Debate