20+ years building massive distributed systems for Amazon, Microsoft, Google, and Uber. Led design and development of the AWS SQS backend, and AWS SWF. Tech lead of OSS Cherami, Cadence and Temporal.
I think the core underlying problem is that there is no standard for asynchronous communication among services. For example how is operation that can take long time is exposed and invoked. Queuing and event sourcing are attempts to workaround this limitation.
I think the real solution is to expose asynchronous service API explicitly and use an orchestration technology to implement the business transaction using such APIs.
I would recommend looking at Cadence Workflow open source platform that supports such orchestration using natural code.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the core underlying problem is that there is no standard for asynchronous communication among services. For example how is operation that can take long time is exposed and invoked. Queuing and event sourcing are attempts to workaround this limitation.
I think the real solution is to expose asynchronous service API explicitly and use an orchestration technology to implement the business transaction using such APIs.
I would recommend looking at Cadence Workflow open source platform that supports such orchestration using natural code.