Don't waste your time listening to this talk. He is advocating for one extreme on the spectrum between orchestration and choreography. The real solution probably lies somewhere in the middle. The amount of issues companies run into when implementing event driven architecture is immense. Most solutions he brings up when avoiding workflow engines in this talk are to waste months rebuilding observability and scaffolding around your code just to understand what is happening. There are so many footguns with event-driven architecture that can become known only AFTER you have implemented your domain. He loves this fire event and it's someone else's problem pattern. It might say a lot about his personality. He probably doesn't pick up after his dog when he takes it for a walk. This type of pattern promotes teams divided by "microservice" where they all claim "I did my job, here is the event, now it's someone elses problem", where no one is responsible for the entire business process.. which is always worst for the business. 28:18 - "Enjoy the organization clarity that it produces" hahaha
Don't waste your time listening to this talk.
He is advocating for one extreme on the spectrum between orchestration and choreography. The real solution probably lies somewhere in the middle. The amount of issues companies run into when implementing event driven architecture is immense. Most solutions he brings up when avoiding workflow engines in this talk are to waste months rebuilding observability and scaffolding around your code just to understand what is happening. There are so many footguns with event-driven architecture that can become known only AFTER you have implemented your domain. He loves this fire event and it's someone else's problem pattern. It might say a lot about his personality. He probably doesn't pick up after his dog when he takes it for a walk. This type of pattern promotes teams divided by "microservice" where they all claim "I did my job, here is the event, now it's someone elses problem", where no one is responsible for the entire business process.. which is always worst for the business.
28:18 - "Enjoy the organization clarity that it produces" hahaha