Hacker News Reader

I feel like microservices are a solution for magpie developers. It's hard to keep a hundred engineers excited about working in an aging Java stack when there's all these shiny new tools out there. But maybe that's just my perspective, coming from a consultancy firm whose devs wanted to stay on the cutting edge.

View on HN

> It's hard to keep a hundred engineers excited about working in an aging Java stack when there's all these shiny new tools out there.

I think you can remove Java in that sentence.

I think this leads to silos. MicroServices written in different lang's mean Java Dev X can't maintain Python service Y.. Not in an efficient way. What's worse, Java Dev can't move to Team Y without upskilling not only on the service, but also the lang, so they get pidgin holed. She also can't move because she's the only Java dev left.

Reply on news.ycombinator.com