Menu

1 / 2

A 5-Person Team, 14 Microservices. How We Got There and Why We Walked It Back

DEV Community: microservices·Kamen·about 4 hours ago
#PJmyKCbK
#devtomicroservices#devto#dev#spring#three
Reading 0:00
15s threshold

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 gateway, and a new engineer typically spent their first two days getting it to boot before touching a line of business code.

We had arrived at fourteen, one reasonable decision at a time. The system started as three services, split along lines that made sense. After that, every new capability that sounded like a separate concern became a separate service, because that was how the architecture diagrams we admired were drawn, and because splitting felt like the responsible, forward-looking choice. Nobody ever proposed having fourteen. Each service was individually defensible, and nobody was in a position to say that the sum of them no longer was.

The cost was not in the code. It was in everything around the code.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.