API design: build contracts that survive change
How to design HTTP APIs around clear resources and contracts: names, methods, validation, errors, pagination, idempotency, versioning and the evidence needed to evolve an API safely.
Read articleInsights
Technical articles on languages, databases, serverless platforms and the awkward realities of keeping systems moving.
Showing 1–4 of 4 Architecture articles
How to design HTTP APIs around clear resources and contracts: names, methods, validation, errors, pagination, idempotency, versioning and the evidence needed to evolve an API safely.
Read articleHow to choose system-design patterns from real product constraints: clear boundaries, data ownership, synchronous and asynchronous coordination, resilience and gradual change.
Read articleA practical guide to layered, hexagonal, vertical-slice, modular-monolith, service, event-driven, CQRS and migration patterns, and the constraints that justify each one.
Read articleHow to distinguish capacity problems from architectural ones, recognise evidence for extracting a service and move a bounded capability without losing data ownership, reliability or delivery speed.
Read articleStart a conversation
A feature that needs shipping, an ageing service that needs attention, or a deployment that has become harder than the code. Talk to us about your problems.