Completed
observability - what happens when things break?
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Building Event-Driven Systems: Principles, Challenges, and Best Practices
Automatically move to the next video in the Classroom when playback concludes
- 1 intro
- 2 preamble
- 3 eda
- 4 james eastham
- 5 you learn much more in failure than you do in success
- 6 aim for low coupling and high cohesion
- 7 why be event-driven?
- 8 what does it mean to be event-driven?
- 9 events are first class citizens... ?
- 10 event carried state transfer
- 11 evolvability - a core feature of event-driven architecture
- 12 now what?
- 13 governance
- 14 so, fat vs sparse events?
- 15 embrace the metadata / data pattern
- 16 asynchronous - what happens when you think async?
- 17 embrace eventual consistency
- 18 observability - what happens when things break?
- 19 boundaries - surely you need synchronous sometimes?
- 20 start small
- 21 thank you for listening
