Paths

Reading paths.

Start with flagship essays See pricing

Paths

Flagship essays

The fastest way to judge whether ArchCrux fits how you think.

Best starting point

Start here, then move into judgment and system boundaries.

Open path

Layer 2/Caching & Data AccessSenior

Cache-Aside: Why It Works, Where It Breaks

Cache-aside is not mainly a cache pattern. It is a miss-path pattern.

Why read thisWhen the familiar pattern stops being safe.

29 min readRead now

Layer 4/Trade-Off ReasoningStaff+

What Actually Breaks First at 10x Scale

The first break at 10x is usually a boundary mismatch, not an abstract scalability limit.

10 min readRead now

Layer 2/Data PatternsStaff

Idempotency as a System Boundary, Not a Header

Treating idempotency as a header-level concern produces fragile systems. Treating it as a boundary property produces stable retry behavior.

11 min readRead now

Boundaries under pressure

A tight shelf around retries, freshness, ambiguity, and service boundaries.

Best starting point

Best if your work lives around retries, duplicate work, or correctness at service edges.

Open path

Layer 2/Data PatternsStaff

Idempotency as a System Boundary, Not a Header

Treating idempotency as a header-level concern produces fragile systems. Treating it as a boundary property produces stable retry behavior.

Why read thisFor the boundary that only appears in production.

11 min readRead now

Layer 2/Caching & Data AccessSenior

Cache-Aside: Why It Works, Where It Breaks

Cache-aside is not mainly a cache pattern. It is a miss-path pattern.

29 min readRead now

Layer 4/Trade-Off ReasoningStaff+

What Actually Breaks First at 10x Scale

The first break at 10x is usually a boundary mismatch, not an abstract scalability limit.

10 min readRead now

Judgment at load-bearing seams

For readers who know the patterns and want the harder call.

Best starting point

Best if you are moving from implementation strength into harder staff-level calls.

Open path

Layer 4/Trade-Off ReasoningStaff+

What Actually Breaks First at 10x Scale

The first break at 10x is usually a boundary mismatch, not an abstract scalability limit.

Why read thisWhen the hard part is judgment, not recall.

10 min readRead now

Layer 2/Data PatternsStaff

Idempotency as a System Boundary, Not a Header

Treating idempotency as a header-level concern produces fragile systems. Treating it as a boundary property produces stable retry behavior.

11 min readRead now

Layer 2/Caching & Data AccessSenior

Cache-Aside: Why It Works, Where It Breaks

Cache-aside is not mainly a cache pattern. It is a miss-path pattern.

29 min readRead now