Event-driven systems & architecture
01:05:24 Share

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 – Mastodon), Twitter), LinkedIn)
• Indu Alagarsamy – Mastodon), Twitter), LinkedIn), Website)
• Viktor Stanchev – Twitter), GitHub), LinkedIn), Website)
• Angelica Hill – Twitter), GitHub), LinkedIn)

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!)