Skip to content

Writing

Notes from building reliable systems

Practical lessons, architectural decisions, and engineering notes from building distributed systems and software that has to hold up in production.

Search the writing

Featured series

A practical series on designing external operations to remain explicit, observable, and recoverable when dependencies fail, responses arrive late, or the outcome is uncertain.

  1. Reliable External Operations Are More Than RetriesStart here
  2. Timeouts Are a Correctness BoundaryComing soon
  3. Retrying Without Making Things WorsePlanned
Show 9 more articles
  1. Idempotency Is a Business InvariantPlanned
  2. The Hard Part Is the Ambiguous OutcomePlanned
  3. Circuit Breakers Are a Decision to StopPlanned
  4. Rate Limits, Concurrency, and BackpressurePlanned
  5. Fallbacks Should Degrade, Not DeceivePlanned
  6. Observability for Work That Crosses BoundariesPlanned
  7. How Reliability Mechanisms InteractPlanned
  8. Testing Failure Paths, Not Just Happy PathsPlanned
  9. From Reliability Patterns to Reusable PrimitivesPlanned

Practical guides

All guides

Project updates

All project updates
  • Project update2 min read

    RelPrim 0.9.0 Adds Provider-Aware Rate-Limit Recovery

    RelPrim 0.9.0 adds provider-aware retry delays, maximum wait enforcement and fallback integration for external operations rejected by rate limits.

    • relprim
    • python
    • reliability
    • rate-limiting
  • Project update2 min read

    RelPrim 0.8.0 Adds Idempotency for Safe Retries

    RelPrim 0.8.0 adds idempotency policies, concurrent execution joining and successful result replay for external operations that must not run twice.

    • relprim
    • python
    • reliability
    • idempotency