Chaos in Fediverse

Jak #business dostat z českého rybníčku do světa.
„Problém detašovaného #sales tak neřeší ani lepší výběrový proces. Chcete totiž od domorodého obyvatele ostrova, aby za banány, které mu posíláte (přestože tam má vlastních dost), stavěl v nové osadě chatrče, přestože vy na tom ostrově nejste a v chatrčích bydlet nebudete.“ https://medium.com/wultra-blog-cz/p%C3%A1r-mega-v-pr-li-aneb-strategie-pro-rozvoj-mezin%C3%A1rodn%C3%ADho-obchodu-%C4%8Desk%C3%BDch-b2b-it-firem-486c4714dac3

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.