Skip to content
AK
← Back to portfolio/ Architecture

Architecture Library

Patterns I have shipped, written to be reused. Each one covers the problem it solves, the structure, what it costs, and when to reach for something else.

Frontend Architecture

Microfrontend Boundaries

Split a frontend along ownership and deploy cadence, not along technical layers or page routes. The boundary is right when a team can ship its surface without coordinating with anyone else.

MicrofrontendsTeam TopologyMigrationFrontend ArchitectureRead pattern →

Platform Design

GraphQL Schema Ownership

Treat the schema as a published contract with named owners and a deprecation policy, not as a type file any team may extend. Federation distributes authorship, which makes ownership the thing that has to be designed.

GraphQLAPI DesignPlatform EngineeringTeam ProcessRead pattern →

SDK Architecture

The Headless and UI Split

Ship an SDK as two layers: a headless core carrying logic, state, and API contracts, and a UI layer built on top of it. Clients take both or take only the core, without either path being second class.

SDK DesignAPI DesignDesign SystemsCross-PlatformRead pattern →