Observability

Problem

What becomes confusing, fragile, or impossible without understanding observability? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

Distributed architectures address concrete capacity, reliability, and coordination limits—but often arrive before those limits do.

Concept explanation

Observability belongs to “Distributed systems without cargo cult”. observability is inspected by introducing one realistic failure and proving root cause before repair.

For observability, trace concrete input, state transition, output, and failure through an architecture decision tied to explicit requirements, estimates, state ownership, failure modes, and measured limits.

Start with requirements and estimates, choose the smallest architecture, locate its first bottleneck, then evolve one measured constraint at a time. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Worked example

Start from supplied design.md. Focus: Capture healthy observability baseline from: Design chat/search from single node, then add one measured distributed constraint at a time.

1. Run: Fill design.md, then verify every component traces to one stated requirement or measured constraint.
2. Save baseline evidence. Trace requests, state ownership, capacity, queues, caches, replication, failure domains, recovery, operational load, and cost.
3. Boundary case: Record observability behavior at: Model partition and replica lag in user-visible terms.
4. Failure case: Diagnose this exact observability failure before editing: Lose leader or duplicate delivery and specify recovery/invariant.

RESULT
Evidence identifies first divergence, repair changes only proven cause, and rerun restores: Diagram names state owner, consistency window, failure domain, trace path, and coordination tax. Starter-level baseline: Document names one action, target, non-goal, numeric estimate, state owner, request path, bottleneck, and recovery procedure.

Starter material

Create design.md, paste this exact content, then run the command below.

# observability

## Requirements
- One primary user action:
- One reliability target:
- One explicit non-goal:

## Estimate
- Requests/second:
- Stored bytes/day:
- Peak concurrent work:

## Smallest design
- State owner:
- Request path:
- First bottleneck:
- Recovery procedure:

STOP / CLEANUPStop any process started by your slice with Ctrl+C; run git status before leaving.

Independent exercise

Prove root cause: observability

1. Create second case from blank file: Record observability behavior at: Model partition and replica lag in user-visible terms.
2. Then create controlled failure: Diagnose this exact observability failure before editing: Lose leader or duplicate delivery and specify recovery/invariant.
3. Use Architecture notebook · load tests · traces · Git history to prove behavior, then repair controlled failure.
4. Compare result against supplied acceptance checks and reference approach before marking complete.

Expected result

• Evidence identifies first divergence, repair changes only proven cause, and rerun restores: Diagram names state owner, consistency window, failure domain, trace path, and coordination tax.
• Document names one action, target, non-goal, numeric estimate, state owner, request path, bottleneck, and recovery procedure.
• Controlled observability failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.