I'm not sure why anyone thought this was a good idea in the first place. I always saw it as a manifestation of Conway's law [0] driven from money printing.
That is, more money -> higher demand for employees -> employees that shouldn't be given authority are -> "I want to code only in <techx that no one uses> -> microservices are the only way I can do this -> microservices are good.
This is quite a snobby video with no substance. He sounds like a guy who applied but never made it to the big tech companies and needs to find something to complain about to feel grander.
Microservices should not be a Swiss Army knife. But so should hating on them completely either…
pros and cons with actual examples would be more useful than an academic toy example. Waste of time and not constructive!
i've never used kubernetes or related 'microservices' tech in a high use environment, so just have no practical experience with microservices, unless you could EJBs?
i can imagine troubleshooting a microservices environment could get hairy, but i've had non-microservices environments get hairy, so...
4 comments
[ 3.1 ms ] story [ 19.0 ms ] threadYou may check: https://www.asyncapi.com/
That is, more money -> higher demand for employees -> employees that shouldn't be given authority are -> "I want to code only in <techx that no one uses> -> microservices are the only way I can do this -> microservices are good.
[0] https://en.wikipedia.org/wiki/Conway%27s_law
and i'm here for it.
but one part i'm confused about is:
i've never used kubernetes or related 'microservices' tech in a high use environment, so just have no practical experience with microservices, unless you could EJBs?i can imagine troubleshooting a microservices environment could get hairy, but i've had non-microservices environments get hairy, so...