Change is inevitable: versioning event-driven systems - Laila Bougria - NDC Oslo 2026

Value of the Information & Strength of the Argument

The value of the information lies in its practical, experience-based insights. The speaker doesn’t just list abstract principles; she provides a concrete example and demonstrates the consequences of poor design decisions, such as introducing functional coupling and poison messages. The argumentation is solid: she logically walks from the problem (contract changes breaking consumers) to a solution (granular events, public/private separation, and schema usage). Her analogy to deleting a social media post effectively communicates the loss of control over public data. The reasoning is persuasive and encourages proactive architectural thinking. The talk is well-structured, each point builds on the previous, and the case study is effective in making the abstract concrete.

Scientific Rigor, Source Quality, Title Accuracy

The talk demonstrates scientific rigor through its use of a real-world example (the NASA Mars Climate Orbiter) and reference to industry concepts like Pat Helland’s work on events on the inside and outside. The speaker also names common serialization formats (JSON, Avro, protobuf) and addresses real problems like in-flight messages and error queues. The title is highly accurate; the content precisely matches the promise of discussing versioning in event-driven systems. No external sources are explicitly cited beyond the general conference links, but the speaker’s expertise and the anecdotal evidence support the claims. The overall rigor is high, though it could benefit from citing specific research or publications beyond the Pat Helland reference.

The title accurately reflects the content, which focuses on how to handle change in event-driven architectures, explicitly addressing versioning.

8/10

The talk is grounded in the speaker's 20 years of hands-on experience with distributed messaging systems. It provides practical, well-structured advice on versioning strategies, clearly explains coupling risks, and refers to established concepts like Pat Helland's work on public/private events. No claims are unsupported or misleading; the reasoning is coherent and aligned with industry best practices.

Markers derived by PSI from the transcript: the creator did not define chapters.

• 02:00Introduction: The speaker introduces herself and sets the context of distributed systems complexity.
• 10:00Credit card transaction example: Introducing the naive event design and initial problems.
• 20:00Functional coupling and its consequences: How adding attributes like 'cost' leads to consumer breakage.
• 30:00Designing granular events and public/private events: Discussing the split and the card period closed summary event.
• 40:00The importance of schemas: Referencing Avro and the NASA Mars Climate Orbiter incident.
• 50:00Versioning strategies and facilitation: Managing in-flight messages and coordinating change across teams.
• 1:00:00Conclusion: Summary of key takeaways and reminder that change is inevitable and must be planned for.

• NDC Conferences — Conference organization hosting the talk.
• NDC Oslo — Conference event where this talk was recorded.
• Pat Helland's paper on events (mentioned in talk) — The speaker references Pat Helland's work on 'events on the inside and outside' as conceptual basis for public/private events.

• Pat Helland's paper on events (mentioned in talk) — Aligns with the talk's recommendation to separate internal and external events.