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 a decade building platforms at scale, I have learned good architecture is mostly owning trade-offs honestly, not chasing the newest pattern.
Articles in this hub
2 articles
microVMs Explained: Firecracker vs gVisor for Secure Workloads in 2026
A practical 2026 comparison of Firecracker microVMs and gVisor for secure workload isolation: how each sandbox works, the security and performance trade-offs, and when to choose KVM-based VMs over a userspace kernel.
Read article →
Why I Moved from Nest.js to Fastify and DDD in 2026
A personal look at why I moved away from Nest.js and chose Fastify with Domain Driven Design for leaner, clearer Node.js backend architecture.
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 →