Architecture as the art of trade-offs, decided with the system in mind.
Architecture is not diagrams — it is the small set of decisions that are expensive to reverse, made well. Service boundaries, where state lives, how components fail and recover: get these right and a system stays cheap to change for years. Across 12+ years building platforms at scale, I have learned good architecture is mostly owning trade-offs honestly, not chasing the newest pattern.
Articles in this hub
4 articles
IntermediateHow to Send 1,000,000 Notifications Without Falling Over
A vendor-neutral system-design walkthrough of the message-queue architecture that sends a million notifications without taking your API down: fan-out workers, back-pressure, retries, and dead-letter queues.
Read article
AdvancedSovereign by Design: Building a Sovereign Platform on Kubernetes
A practical 2026 architecture for digital sovereignty: treat sovereign cloud as three layers — data, operational, technical — and use Kubernetes, external key custody, and a real exit path to make sovereignty a design property instead of a marketing sticker.
Read article
AdvancedSecure-by-Default GKE: A Reference Architecture for 2026
A practical secure-by-default GKE reference architecture for 2026: defense in depth across identity, network, supply chain, admission, runtime, and observability — with Workload Identity Federation and Binary Authorization at the core.
Read article
AdvancedPub/Sub or Eventarc? Event-Driven GCP Without the Spaghetti
When to reach for Pub/Sub, when for Eventarc, and how to keep an event-driven GCP system clean: idempotency, dead-letter queues, and the trap of fan-out spaghetti.
Read article
FAQ
What is your architecture background?
Are you available to hire?
How do we start working together?
Designing a system you have to live with?
From service boundaries to event-driven design and resilience, I help teams make the expensive-to-reverse decisions well — and keep the architecture cheap to change.
See architecture services →