In software architecture you have to recognize when you're adding a rocket stage.
In rockets and aeroplanes it's a simple truth that weight adds more weight. To carry more you need bigger engines, a bigger fuel thank, more fuel. More weight becomes even more weight.
For rockets to make it out of the atmosphere they use multiple stages. Each stage carries the rocket to a certain height, once the fuel is used up the stage is ejected so the next stage can push forward a lighter rocket. So adding a stage will get you further, but at the cost of much more machinery, engineers, and complexity. You now have a much heavier rocket to launch.
Switching to kubernetes, kafka, microservices, a single page app, ... is adding a rocket stage. Maybe it's what you need to get where you want to go, but be clear about the extra weight, operational cost, engineering overheard, mental overhead.
Za mě je požadovaný stav, kdy má entita ve vzájemném kontaktu stejná práva bez ohledu na to jestli je fyzická nebo právnická (jedinec versus firma/stát).
I think we're focused on the wrong thing when we look at what tech works for a company like Amazon or Facebook or Netflix.
We should be looking at what tech works when you *don't* have a small army of staff engineers optimizing it. I want to know what I can scale *without* paying someone a half million dollar salary to do it.
There should be more case studies on things that don't have a billion-dollar company propping them up, humming along quietly on a cheap-ass VPS somewhere.