2 ms·
> However one of the unexpected consequences How the hell... like... who decided to do Microservices in the first place if they didn't know this? This is such
by 0xblinq 4y ago
> However one of the unexpected consequences
How the hell... like... who decided to do Microservices in the first place if they didn't know this? This is such a rookie mistake. It's like somebody right out of high school just read on a blog the new way is "microservices" and then went ahead with it.
- Pamar 4y agowell, this is a surprisingly common case in my experience, except that the people were not "right out of high school" but "right out of a company funded seminar on microservices".
- marcosdumay 4y agoThere is a high amount of correlation between people that start with microservices (instead of using them to solve specific problems after they have the problem) and people that lack any awareness about the resources they need. And both are way more common than they should be.
- dogleash 4y ago>How the hell... like... who decided to do Microservices in the first place if they didn't know this? Microservices can have both design utility and simultaneously been a major fad. Lurking reddit and HN you can watch development fashions come and go. It's really really profoundly hard to hold a sober conversation on splitting merits from limitations in the middle of the boom. tl;dr: gartner_hype_cycle.png