Learning path / Editorial roadmap

NightLens: system design decisions

A five-lesson course from requirements to controlled overload for a fictional telescope reservation service.

5 articles available · 5 proposed modules

Read at your own pace. This is a growing editorial plan, not a complete course or a progress tracker. Proposed topics have no lesson pages yet.

Explore the path

  1. 1 article available

    Define the promise

    Write a design brief for NightLens, including one-owner slot allocation, explicit SLO denominators, maintenance closures, and an offline-booking trade-off.

  2. 1 article available

    Size the workload

    Convert an assumed telescope-session release into read and booking workloads, a latency budget, Little’s law estimates, and a bounded capacity experiment.

  3. 1 article available

    Protect ownership

    Design NightLens slot locking, database constraints, scoped idempotency, read-after-write behavior, and a transactional outbox with explicit limits.

  4. 1 article available

    Bound stale reads

    Walk through an old-reader refill race and a source-anchored expiry policy for public telescope availability, with coalescing and bounded database fallback.

  5. 1 article available

    Control failure

    Finish the NightLens design with booking admission limits, honest unknown outcomes, isolated delivery, retry ownership, and recovery tests.