The guarantee you are actually selling

Designing systems that stay correct when everything is on fire

Key Takeaways & Production Insights

01Choose an isolation level from the failure you are preventing, not from habit
02Design reconciliation that catches drift before your customers do
03Reason about partial failure without hand-waving
04Run an incident where the data, not the service, is the casualty

Tools & Systems Used in this Session

PostgresKafkaJepsenOpenTelemetry

Course Outline

0 / 16 Lessons

Module 013 sessions

Foundations

Module 024 sessions

Core Concepts

Module 034 sessions

Real-World Systems

Module 043 sessions

Advanced Techniques

Module 052 sessions

Final Project

Faculty

Amara Oyelaran

Principal Engineer, Distributed Systems

Amara spent eleven years on the unglamorous half of infrastructure — the consistency guarantees, the reconciliation jobs, the 3am pages. She teaches the thing most systems courses skip: how to decide what you are allowed to get wrong, and what you are not.

Lesson 01.0118m

Click to stream instruction

The guarantee you are actually selling18m

Module 01 · Foundations