Backend engineer. I write about what production actually asks of a system that a whiteboard never does.
A design looks clean until real traffic, real failure modes, and real trade-offs show up. This site is where I work through that: what held, what needed a second pass, and what I’d do differently now. Written in public, without pretending it was clean the first time.
A separate system-design library on this site: concept explainers and full case studies, each with a working diagram, not a slide.
Foundations
4 topics
Foundations
5 topics
Foundations
5 topics
Foundations
5 topics
Foundations
5 topics
Foundations
2 topics
Foundations
7 topics
Case Studies
1 case study
Case Studies
0 case studies
Case Studies
1 case study
Three ways a public guest-generation endpoint at Kredvox trusted the client: a forged IP header, a rate-limit TTL that never reset, and an IP address mistaken for an identity. How each was found and closed.
How Kredvox built a typed error contract from Spring Boot to TypeScript, enforced at the build with ArchUnit and ESLint. A pattern that makes the typo class of bug impossible.