HackerTube.dev

The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017

GOTO Conferences · 677K views · 2017-05-11 · 50:06

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

Martin Fowler's GOTO Chicago 2017 talk on the different things people mean by event-driven architecture. He identifies four patterns, including event notification and event-carried state transfer.

On Hacker News

Cited as a useful taxonomy for pinning down what an event-driven design actually is.

Recommended by 1 HN people across 1 months · HN mentions 2018–2022

Topics

Search by tags

What people said

dathinab · 2020-03 · Recommendation

I think that one was good: - [VIDEO] I wasn't able to find any other talk I watched back then or any of the stuff I did read, but I then last time I looked into talks and reading material about this was ~2.5 Years ago and while a lot of new software and tooling was done since then the principles didn't change. Try some of the other GOTO; talks about it if you like listening to talks, they tend to be quite good. This was interesting as far as I remember but not what I was looking for: - [LINK]

Read the original HN comment ↗
nivertech · 2022-08 · Reference

You're right about microservices, but IMO you're mistaken Event Sourcing (CQRS/ES)[1,2] with EDA (Event-Driven Architectures)[3] in general. There are many different types of EDAs. There are at least 3 relevant dimensions when choosing a Software Architecture: 1. complexity of the domain 2. scalability requirements 3. company stage / number of developers working on the same codebase Microservices are mostly solving #3, and to a lesser extent #2. They mostly solve the problem of too many developers blocking each other on a monolithic codebase (NOTE: monolithic doesn't mean non-modular). Event Sourcing and friends (DDD, CQRS, EventStorming, etc.) are mostly solving #1. It's also technology/vendor-agnostic, so makes migration to other tech (including microservices) easier, and most importantly possible at all. So for a complex domain in a small company I would choose a CQRS/ES monolith, but for a simple domain and high scalability in a large company maybe CRUD-based microservices are making more sense. -- [1] [LINK] [2] [LINK] [3] The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017 [VIDEO] What do you mean by “Event-Driven”? [LINK] tagged by: event architectures [LINK]

Read the original HN comment ↗
leoc · 2018-03 · Reference

As a first-class language feature this goes back at least to 1985 and Linda [LINK] and tuplespaces. (You'd know about Linda already if you'd read Concepts, Techniques, and Models of Computer Programming . Don't delay, read CTM today: [LINK] ) And here's a Martin Fowler talk about the practise of implementing it informally as a pattern or framework: [VIDEO]

Read the original HN comment ↗

Sources

Video by GOTO Conferences, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources