Top 5 techniques for building the worst microservice system ever - William Brander - NDC Porto 2023

[@jeroenj7494]

1) use microservices?

[@roeniss]

lol

[@JulianSildenLanglo]

I wish they'd do a bit of audio processing, it's really tinny.

[@FlaviusAspra]

22:30 that right there is the mistake "the new system talks to the old system". This is wrong because your strategic goal is to turn off legacy at some point, so what you want to do is: * Communication is always initiated by the old system. This way, you can start turning off business capabilities in legacy as they get strangled, while still delivering business value You want to optimize and plan for "turning off legacy", such that when you turn off parts of legacy, everything still works.

[@FlaviusAspra]

Regarding strangling: what matters is the abstraction level at which you strangle. If you strangle too low, you create the mess shown in the presentation. But if you strangle high-level enough, meaning a business capability at a time, you do it better because: * not as many network calls * the new system is not aligned to technicalities, but to business capabilities. This kind of thinking also inadvertently aligns with bounded context and with vertical slices. It requires: * experience * discipline * systems thinking, empathizing with the business goals