ArchCrux

Flagship reading

Start with the essays that show the standard.

The clearest entry into how ArchCrux thinks.

Cache-Aside: Why It Works, Where It Breaks

Cache-aside works because it keeps the database authoritative, but it breaks where freshness and concurrency assumptions stop being true.

Why read thisWhen the familiar pattern stops being safe.

9 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.

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.

Why read thisFor the boundary that only appears in production.

11 min readRead now

Failure-first editorial

Trade-offs, not trivia

Built for harder calls

Paths

Reading paths.

Path

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 AccessSeniorFree

Cache-Aside: Why It Works, Where It Breaks

Cache-aside works because it keeps the database authoritative, but it breaks where freshness and concurrency assumptions stop being true.

Why read thisWhen the familiar pattern stops being safe.

9 min read

Author

ArchCrux Editorial

AE

Founding editorial voice

Writing about backend systems under production pressure.

Membership

Read free. Subscribe for the full library.

Free

$0

Read before you pay.

Flagship essays

Public notes

Browse essays

Read free essays

Annual

$240/year

Best for regular readers.

Full article library

Reading paths

Bookmarks

New essays

View annual pricing

Sharper backend judgment for engineers already living with production consequences.

Cache-Aside: Why It Works, Where It Breaks

Start with the essays that show the standard.

Cache-Aside: Why It Works, Where It Breaks

What Actually Breaks First at 10x Scale

Idempotency as a System Boundary, Not a Header

Failure-first editorial

Trade-offs, not trivia

Built for harder calls

Reading paths.

Flagship essays

Cache-Aside: Why It Works, Where It Breaks

ArchCrux Editorial

Read free. Subscribe for the full library.

$0

$240/year

What Actually Breaks First at 10x Scale

Idempotency as a System Boundary, Not a Header

Boundaries under pressure

Idempotency as a System Boundary, Not a Header

Cache-Aside: Why It Works, Where It Breaks

What Actually Breaks First at 10x Scale

Judgment at load-bearing seams

What Actually Breaks First at 10x Scale

Idempotency as a System Boundary, Not a Header

Cache-Aside: Why It Works, Where It Breaks

$24/month