Go Time – Episode #297

Event-driven systems & architecture

with Chris Richardson, Indu Alagarsamy & Viktor Stanchev

All Episodes

Event-driven systems may not be the go-to solution for everyone because of the challenges they can add. While the system reacting to events published in other parts of the system seem elegant, some of the complexities they bring can be challenging. However, they do offer durability, autonomy & flexibility.

In this episode, we’ll define event-driven architecture, discuss the problems it solves, challenges it poses & potential solutions.



FastlyOur bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com

Fly.ioThe home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.

Typesense – Lightning fast, globally distributed Search-as-a-Service that runs in memory. You literally can’t get any faster!

Notes & Links

📝 Edit Notes


1 00:00 It's Go Time!
2 01:21 Viktor Stanchev
3 02:10 Indu Alagarsamy
4 03:01 Chris Richardson
5 03:45 What is event-driven architecture?
6 13:57 Orchestration vs choreography
7 19:00 All the tradeoffs
8 40:16 Bringing this to the wild
9 48:00 Risks of change
10 53:12 Final conclusions
11 56:27 Unpopular opinions!
12 56:50 Viktor's unpop
13 58:53 Chris' unpop
14 1:00:38 Indu's unpop
15 1:04:06 Outro


⏰ Coming Soon


We're hard at work on the transcript for this episode! Sign in / up to access transcript notifications. 💪

Player art
  0:00 / 0:00