seems like a bit of a meaningless discussion without talking about a specific example.<p>and i'm here for it.<p>but one part i'm confused about is:<p><pre><code> horizontal scaling == microservices == k8s == containers == true?
</code></pre>
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?<p>i can imagine troubleshooting a microservices environment could get hairy, but i've had non-microservices environments get hairy, so...
"There is no good and standardised way of expressing asynchronous APIs."<p>You may check: <a href="https://www.asyncapi.com/" rel="nofollow">https://www.asyncapi.com/</a>
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.<p>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.<p>[0] <a href="https://en.wikipedia.org/wiki/Conway%27s_law" rel="nofollow">https://en.wikipedia.org/wiki/Conway%27s_law</a>