WordloopSystem Design
The structural commitments that determine whether a system stays tractable as it grows.
System Design
System design is where abstract principle meets concrete structure. The choices in this section — how we shape services, how our APIs evolve, how real-time flows handle backpressure, how data moves, how systems integrate with each other — are the ones that compound most heavily as the platform grows.
Hexagonal architecture is the cornerstone. It appears first in this list deliberately. Every other page here assumes that services are internally structured as ports and adapters around a domain core — if that assumption collapses, nothing else we write about system design applies cleanly.
Hexagonal Architecture
Ports, adapters, unidirectional dependency flow, and why this structure is the single highest-leverage choice for an agent-led codebase.
API Design
Contract-first design, versioning, evolution, pagination, and AI-agent readiness.
Real-Time
WebSockets, streaming, backpressure, echo suppression, and the resiliency patterns that make live experiences survive degraded networks.
Data Engineering
Events, streams, CQRS, event sourcing, and the data contracts that outlive any service.
Integration Patterns
Webhooks, the outbox pattern, idempotency, and the sync-vs-async trade-off.