Event-driven systems & architecture

Go Time: Golang, Software Engineering

Content provided by Changelog Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Changelog Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

2y ago 1:05:24

MP3•Episode home

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on May 12, 2025 15:45 (7M ago)

What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

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.

Join the discussion

Changelog++ members save 1 minute on this episode because they made the ads disappear. Join today!

Sponsors:

Fastly – Our 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.io – The 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!

Featuring:

Chris Richardson – LinkedIn, Mastodon, X
Indu Alagarsamy – Website, LinkedIn, Mastodon, X
Viktor Stanchev – Website, GitHub, LinkedIn, X
Angelica Hill – GitHub, LinkedIn, X

Show Notes:

Temporal
NServiceBus
MassTransit
Transactional Outbox Pattern
Choreography vs orchestration
Event sourcing
CQRS
Messaging Channels
Cloud-based workflow solutions
- GCP Workflows
  - GCP workflows yaml language
- AWS Step Functions
  - “Amazon states language” based on json
Go specific microservices orchestration tools, frameworks, and libraries:
- Temporal Go SDK
- Watermill
Software Architecture as a Set of Architectural Design Decisions

Something missing or broken? PRs welcome!

Chapters

1. It's Go Time! (00:00:00)

2. Viktor Stanchev (00:01:21)

3. Indu Alagarsamy (00:02:10)

4. Chris Richardson (00:03:01)

5. What is event-driven architecture? (00:03:45)

6. Orchestration vs choreography (00:13:57)

7. All the tradeoffs (00:19:00)

8. Bringing this to the wild (00:40:16)

9. Risks of change (00:48:00)

10. Final conclusions (00:53:12)

11. Unpopular opinions! (00:56:27)

12. Viktor's unpop (00:56:50)

13. Chris' unpop (00:58:53)

14. Indu's unpop (01:00:38)

15. Outro (01:04:06)

348 episodes

#Cloud IT #Golang #Open Source #Software #Development #Changelog Media #Tech #Architecture #Docker #Kubernetes #Industries #DevOps

Event-driven systems & architecture

Go Time: Golang, Software Engineering

983 subscribers

published 2y ago

MP3•Episode home