postmodern.tf

Patterns

The concepts behind the systems.

A pattern is a problem with forces pulling against each other, a solution that resolves them, and the trade-offs you accept by choosing it. Each one here names the blueprints that use it and the components that implement it.

Maturity

Draft
Captured, not yet reviewed.
Documented
Problem, forces and trade-offs written down.
Composed
Used by a reference architecture.
Production
Running on a live site.
Three abstract diagrams: a source resolving into a projection, a path splitting in two, and one event fanning out to several consumers

Catalogue

06 patterns · in progress

  1. Draft

    Materialized View

    Precompute a read-optimized projection so queries stay fast without recomputing on every request.

  2. Draft

    CQRS

    Separate the write model from the read model so each can be shaped for its own job.

  3. Draft

    Event-Driven Fan-out

    Publish one event and let independent consumers react, without the producer knowing who they are.

  4. Draft

    Private Origin

    Serve a private backend through CloudFront without exposing it to the internet.

  5. Draft

    Edge Blue/Green

    Shift traffic between two backend deployments at the edge, with canary weighting and cookie pinning.

  6. Draft

    Edge Configuration

    Keep routing and rollout configuration in Parameter Store and project it to the edge.

Patterns are written down as they are earned. The catalogue grows from the architectures in production, not ahead of them.

Where patterns live

Concepts become systems.

A blueprint assembles several patterns into a working architecture. Each pattern points at the blueprints that express it and the components that build it, so you can move from the idea to running code.

Explore blueprints ↗