Notes on decisions from real systems.
I write about engineering decisions together with their constraints, the options I rejected, and the point where the chosen approach stops working.
- 01
Runtime14 min read
Spring Boot: are we native yet?
What I learned taking a Kotlin/Spring Boot commerce service native: adoption, testing, startup, memory, and the tradeoffs of a 0.25 vCPU Fargate task.
- 02
Reliability9 min read
What eight billion requests a day teaches you about smaller systems
Budgets, partial failure, operations, and the cost of every boundary: four lessons from Adobe-scale infrastructure, resized for a single small service.
- 03
Delivery10 min read
Handover is part of the product
A handover that works is designed into delivery: role guides checked like software, alerts that point to runbooks, controlled releases, explicit ownership.
- 04
Product engineering9 min read
Availability is a decision, not a property
A product can be published, discoverable, offered, and fulfillable on different terms. Store those facts separately and resolve availability per request.
- 05
Architecture11 min read
Static, edge, or live: decided per path
How one storefront splits its paths: pages prerendered to the edge, money paths on a live origin, and publishing controls that keep content drift visible.
Two ways to work together
For a product or platform that needs to be built, modernized, or operated, start with AG Systems. For a senior or lead engineering role, write to me directly.