Reading path

Frontend Architecture

A curated reading path for architects choosing composition patterns, platform extensibility, and real-time systems at scale.

For architects and senior engineers choosing how to split, extend, and scale frontend platforms — not just which framework to pick.

Composition patterns

Follow the Micro Frontends series in order:

  1. Micro Frontends: Why? — When independent deploys beat a shared release train — and when they do not.
  2. Micro Frontends: How? — Client-side composition with custom elements, and the contract the companion actually uses.
  3. Micro Frontends: Working Example — Qwik shell, Angular and React remotes, live demo.

When not this pattern

  1. Micro Frontends vs Monorepo vs Shared Module — A standalone decision piece: when a monorepo or a library is the better call.

Platform extensibility

  1. Building Custom Angular Schematics — Automating code generation for platform teams.
  2. Custom Web Components with Stencil in Angular — Framework-agnostic components inside Angular apps.

Real-time and performance

  1. Real-time Data in Frontend Applications — Patterns for live data without melting the UI.
  2. Angular Web Workers and OffscreenCanvas — Offloading heavy work from the main thread.

Design systems

  1. The Cost of Consistency: Design System Bottlenecks — Lessons from building a design system without the rigidity trap.

Delivery and authority

  1. The Frontend Is a Privileged System Now — Repositories, install hooks, and release identities are architectural boundaries. The browser is untrusted; the system that delivers the bundle often is not.