Since the micro-service craze started, I've been yelling this from the rooftops. Making everything a micro-service by default is pure insanity. The overhead to maintain them requires exponentially more resources than a monolith or a few services. A few weeks before I left my last job, a very high level engineer gave a presentation where he stated, in all seriousness, that we should be producing one micro-service per day with the goal to be two per day after one year. I didn't need any motivation to leave but that would have done the trick.
You should have marked this comment with a warning.
"One micro service per day" is the most ridiculous thing I have heard in a long time and I also threw up a little.
I feel like most of the best paying companies are emphasizing microservices (except maybe Google). This is just my impression and I realize it's probably not accurate.
What are some solid companies with competitive pay that only use microservices when the need arises instead of by default, using monoliths otherwise?
The problem is that the term “microservices” was so much catchier than “service oriented architecture” that people went overboard with it. Macroservices are a much better idea imo.
Since the micro-service craze started, I've been yelling this from the rooftops. Making everything a micro-service by default is pure insanity. The overhead to maintain them requires exponentially more resources than a monolith or a few services. A few weeks before I left my last job, a very high level engineer gave a presentation where he stated, in all seriousness, that we should be producing one micro-service per day with the goal to be two per day after one year. I didn't need any motivation to leave but that would have done the trick.