Automating Processes in Modern Architectures • Bernd Rücker • GOTO 2020

[@mbalins]

yeeess, please more of these videos with timestamps

[@maxkossatz6731]

Kogito is my favourite Kubernetes-native serverless workflow develipment and management tool!

[@LeandroStoroli]

Maybe distributed tracing can help tracking the business flow and which services were involved on a particular business operation?

[@berndruecker6433]

Hi Leandro, thanks for the feedback. I looked a bit on the shortcomings of distributed tracing for that use case in www.infoq.com/articles/monitor-workflow-collaborating-microservices/ - happy to discuss!

[@Bartek0419]

It's quite naive. To be honest, I don't see the justification for introducing aditional latency cost and coupling just to have the whole workflow visible in one place, there are other solutions to achieve that. And workflows if they are well defined they do not change overnight.

[@Jonathan1234000]

Agile business is literally changing business processes / workflows overnight... thats the point of this technology. Enabling more efficient / failure resistent business. The same reason computers, distributed systems, microservices and every other architecture came to be. I don't know if you ever had to coordinate different deployments because you wanted to make a little change to a process. It's not agile and there are lots of ways it can go wrong. Basically an organisational monolith. And thats only one of the problems solved by workflow engines. Its a way to get distributed systems under control.