1 HN user recommended this talk1 month2018–2022score 1
Years with an HN recommendation, 2007–2026
Cited as a useful taxonomy for pinning down what an event-driven design actually is.
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.
“This was interesting as far as I remember but not what I was looking for” (HN, 2020)
I think that one was good: - [this 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]
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: [this video]
Martin Fowler on implementing message-oriented design as a pattern or framework.
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 [this video] What do you mean by “Event-Driven”? [link] tagged by: event architectures [link]
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
4 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Citations, criticism and jokes
Read more