Every Event, Everywhere, All at Once • Jacqui Read • GOTO 2025

Item: Every Event, Everywhere, All at Once • Jacqui Read • GOTO 2025
Rating: 4
Author: PostSingularity Institute

by Jacqui Read

Applied Sciences & Engineering Computing & Cybersecurity UYZHuman–computer interaction UYZGUser interface design and usability

🎙 Jacqui Read 👥 1.1M 📅 August 25, 2026 ⏱ 37 min 👁 26 📄 expert opinion 🧭 2026-08-25

Available in: English (current) Français

Keywords

eventcommandevent sourcingevent streamingtombstone event

Summary

In this GOTO 2025 talk, Jacqui Read provides a comprehensive disambiguation of event-related terminology in software architecture. She starts by defining what an event is, emphasizing that it represents something that has already happened, contrasting it with commands which express intent. She then explores event streaming, explaining message logs and offsets, and contrasts it with message queues. The talk covers event-driven architecture (EDA), highlighting how it reduces coupling compared to command-driven approaches. EventStorming is introduced as a collaborative modeling technique, with pivotal events marking transitions between bounded contexts. Event sourcing is explained as storing state changes as events, similar to version control, and the concept of an event store is clarified. Tombstone events are discussed as markers for data deletion or retry completion. The speaker distinguishes domain events from integration events, offering new terminology to reduce confusion. Finally, she addresses event granularity, advising to keep events as small as possible but as large as necessary. Throughout, she uses relatable analogies (e.g., Star Trek) and practical examples to illustrate key points.

170 words

Critical Evaluation

Value of the Information & Strength of the Argument

The talk provides high value by systematically clarifying a notoriously confusing area of software architecture. The speaker’s argumentation is solid, building concepts progressively and using clear definitions, analogies, and practical examples. She effectively contrasts commands vs. events, message logs vs. queues, and domain vs. integration events, offering actionable guidance. The use of historical context (JDK 1.1 events) and references to authoritative sources (DDD reference, Confluent) strengthens the credibility. The argumentation is coherent and well-structured, though some topics (e.g., event sourcing internals) are covered at a high level.

Scientific Rigor, Source Quality, Title Accuracy

The talk demonstrates strong scientific rigor in its use of established terminology and references. The speaker cites the DDD reference book, the Confluent blog for error-handling patterns, and the event-driven.io article on events vs. commands, among others. She also references her own book and the ACED model. The title accurately reflects the content, which is a comprehensive tour of event-related concepts. The talk is well-organized, with clear timecodes and a logical flow. The sources are relevant and authoritative, though some are not deeply explored. Overall, the rigor is high for a conference talk.

195 words

Title / Content Match

The title accurately reflects the content: a comprehensive tour of event-related concepts in software architecture, covering many types and patterns.

Quality & Reliability

8/10

The talk is a well-structured expert overview of event-driven architecture concepts, grounded in established terminology and practical experience. The speaker references authoritative sources (e.g., DDD reference, Confluent blog) and provides clear definitions and distinctions. Minor limitations: some concepts are presented without deep technical detail, and the talk is opinion-based rather than empirical.

Chapters

Cited Sources

ACED Model — Referenced as a resource for the talk.
Jacqui Read's website — Speaker's personal site with more information.
Event vs. Command (event-driven.io) — Referenced for the distinction between events and commands.
Tombstone (programming) - Wikipedia — Referenced for the concept of tombstone events.
Error Handling Patterns in Kafka (Confluent) — Referenced for the pattern of maintaining order of redirected events.
Domain-Driven Design Reference — Referenced for the definition of domain events.
Java EventObject documentation — Referenced as an example of early event modeling.
Java PreferenceChangeEvent documentation — Referenced as an example of early event modeling.
Wiktionary definition of event — Referenced for the definition of an event.
GOTO Copenhagen 2025 session page — Link to the full abstract and slides.

Concurring Sources

Domain-Driven Design Reference — Supports the definition of domain events.
Error Handling Patterns in Kafka (Confluent) — Supports the discussion of tombstone events in streaming.
Event vs. Command (event-driven.io) — Supports the distinction between events and commands.

External References

Contribution & Novelties

The talk provides a valuable synthesis of event-related terminology, clarifying often-confused concepts and offering practical guidance on when to use each pattern. It introduces a new perspective on domain vs. integration events, suggesting alternative terminology to reduce ambiguity. The speaker’s use of analogies and real-world examples makes the content accessible while maintaining technical depth.

Pour aller plus loin :

Event-driven architecture - Wikipedia — Provides a broad overview of EDA concepts.
Domain-Driven Design - Wikipedia — Context for domain events and bounded contexts.
Event sourcing - Martin Fowler — A foundational article on event sourcing.
EventStorming - Wikipedia — Explains the collaborative modeling technique.
The Difference Between Events and Commands - Event-Driven.io — Directly relevant to the talk’s core distinction.

120 words

Radar Profile

The radar profile shows high scores across all dimensions, indicating a well-balanced talk with substantial information, good quality, solid technical depth, and high reliability. The talk excels in providing clear explanations and practical insights, making it a valuable resource for software architects.

Reliability 8/10