---
title: "kamen (@kamen-ivanov) | Hashnode"
description: "Team Lead and Senior Backend Engineer with 11+ years building Java and Spring Boot systems. I write about architecture that survives changing requirements, t..."
url: "https://hashnode.com/@kamen-ivanov"
---

@kamen-ivanov

# kamen

@kamen-ivanov · Varna, Bulgaria · Joined July 2026

### [A 5-Person Team, 14 Microservices. How We Got There and Why We Walked It Back](https://pureengine.hashnode.dev/a-5-person-team-14-microservices-how-we-got-there-and-why-we-walked-it-back?utm_source=hashnode&utm_medium=feed)

The first line of our local setup guide was a warning that you needed 24 GB of RAM. Running the whole system on a laptop meant starting fourteen services, three databases, a message broker and a gatew

4 min read · [pureengine.hashnode.dev](https://pureengine.hashnode.dev/a-5-person-team-14-microservices-how-we-got-there-and-why-we-walked-it-back?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/a-5-person-team-14-microservices-how-we-got-there-and-why-we-walked-it-back/6afacd70d1cb62a88978223f)

### [We Debugged "Random" 502 Errors for 2 Days. The Answer Was in One HTTP Header Nobody Looked At](https://pureengine.hashnode.dev/we-debugged-random-502-errors-for-2-days-the-answer-was-in-one-http-header-nobody-looked-at?utm_source=hashnode&utm_medium=feed)

The 502s hit about one login in fifty, and they looked completely random, which is the worst possible bug. Our application logs showed a clean 200 for every one of those requests. Our monitoring showe

4 min read · [pureengine.hashnode.dev](https://pureengine.hashnode.dev/we-debugged-random-502-errors-for-2-days-the-answer-was-in-one-http-header-nobody-looked-at?utm_source=hashnode&utm_medium=feed)

[5d ago](https://hashnode.com/posts/we-debugged-random-502-errors-for-2-days-the-answer-was-in-one-http-header-nobody-looked-at/6af5c5cd5c12b5ed95960268)

### [The Contract Ships Before the Server Does (Chapter 15)](https://pureengine.hashnode.dev/the-contract-ships-before-the-server-does-chapter-15?utm_source=hashnode&utm_medium=feed)

A jar that describes what the server will say, two representations of one product, and a price that is not a number.

18 min read · [pureengine.hashnode.dev](https://pureengine.hashnode.dev/the-contract-ships-before-the-server-does-chapter-15?utm_source=hashnode&utm_medium=feed)

[Nov 9](https://hashnode.com/posts/the-contract-ships-before-the-server-does-chapter-15/6af17a171145eb2306576747)

### [Our Async Event Tests Passed 9 Times Out of 10. The Flakiness Was Hiding a Real Race Condition](https://pureengine.hashnode.dev/our-async-event-tests-passed-9-times-out-of-10-the-flakiness-was-hiding-a-real-race-condition?utm_source=hashnode&utm_medium=feed)

The test failed about once in every ten CI runs, which is rare enough to ignore and frequent enough to hate. It covered a simple flow: an order was saved, an event was published, and an asynchronous l

4 min read · [pureengine.hashnode.dev](https://pureengine.hashnode.dev/our-async-event-tests-passed-9-times-out-of-10-the-flakiness-was-hiding-a-real-race-condition?utm_source=hashnode&utm_medium=feed)

[Nov 6](https://hashnode.com/posts/our-async-event-tests-passed-9-times-out-of-10-the-flakiness-was-hiding-a-real-race-condition/6aedb23cb33b3f3f16ae88fe)

### [The Schema Three Chapters Were Already Relying On (Chapter 14)](https://pureengine.hashnode.dev/the-schema-three-chapters-were-already-relying-on-chapter-14?utm_source=hashnode&utm_medium=feed)

A unique constraint that did not exist, a column type that decides whether inserts batch, and the one decision a database can enforce that code cannot.

24 min read · [pureengine.hashnode.dev](https://pureengine.hashnode.dev/the-schema-three-chapters-were-already-relying-on-chapter-14?utm_source=hashnode&utm_medium=feed)

[Nov 2](https://hashnode.com/posts/the-schema-three-chapters-were-already-relying-on-chapter-14/6ae858472b4ed1ce2d3ef2e0)
