Hacker News Reader

What would be the engineers doing otherwise? You get bored if you don’t.

It's insane to hear attrition used as an excuse for architectural decisions, but I've seen it firsthand.

So we're going to get to the point where everyone gets their own microsevice, right?

That is unironically a better way to do it than anywhere I've worked that does microservices.

My experience with microservice shops is you have one macromonolith with 50 people working on it (which has all the problems of a monolith and none of the benefits), 5 actual decent microservices with a team or individual that properly maintains them, and 100 random utility micro"services" that are like 3 lines of code, used by exactly one other service, and you need 40 loc and a network call to interact with them.

I'll take everyone has their own service any day of the week. At least when I need to interface with 12 different things I can have 12 different people to roast for not properly documenting their API. And tbh literally the only positive I can come up with for microservices is the ability to neatly fire one into the sun and rewrite it from scratch.

Isn’t that basically what happens when you split an API out to the different methods and write a Lambda for each one?

Reply on news.ycombinator.com