Why I Built a Centralised Platform Admin in a Microservices Architecture -And What I Learned

It Started With a Slack Message Our CTO posted in #engineering at 9:47 AM on a Tuesday: "Can someone tell me how many active users we have across all products right now?" Silence. For forty-five minutes. Not because nobody cared - because nobody knew . The auth service had login counts. The user service had registration numbers. The billing service knew who was paying. But no single place could answer: "How many active users do we have?" That Slack message cost us a morning of three engineers querying different databases and reconciling numbers in a Google Sheet. That's when we knew we had a problem. The Microservices Hangover Here's the thing nobody warns you about in the "Why Microservices" blog posts: decentralisation is fantastic for business logic and terrible for everything else. We had twelve services. Each one managed its own roles. Its own permissions. Its own metrics. Its own version of the truth. And when anyone outside engineering asked a straightforward question - "Who has