Hacker News Reader

Comment by addicted44 | Hacker News Reader

It's almost like microservices make sense when they make sense, and macroservices (or, as I like to call them, services) make sense when they make sense, and it's our job as professionals to make those calls.

Nah...we should just pick one and laugh at everyone who doesnt make the same choice until 3 years later we pick the other and then laugh at everyone who hasnt refactored and switched as well.

View on HN

When I first heard of microservices, it confused the hell out of me when I tried to define my company's code base. In some ways we had microservices, for other applications or features we were working on a monolithic service. I used to think it was my lack of understanding, but I eventually realized our code didn't have a binary definition that all the blog posts I was reading seemed to apply to.

I feel like we should have been using verbs this whole time. At least when applying it to legacy systems. Similar to say for databases we can normalize data, or denormalize data. Is there a verb for this already?

I must not be alone in the macroservice to microservice spaghettification migration. If you spend a minutes detangling headphones, but stop half way into it, that's where we're at. At which point, please just give me the monolith. I can accept it isn't the correct architectural vision. Let novel services the business identifies be properly implemented as true microservices. A pinch of pragmatism can go a long way.

Reply on news.ycombinator.com