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 have a question on why Kafka is still used with Cadence for this use case? I believe it would be much simpler if you fully converted all the cross service communication to Cadence. Transfer-websockets service would implement an activity and external writer can start the workflow directly instead of publishing to the Kafka topic.
Good point! To be honest, it did not occur to me but I see what you mean.
It sound like a good material for a new post :-)
I will work on that, stay tuned!
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.
Víctor, thanks a lot for the great tutorial!
I have a question on why Kafka is still used with Cadence for this use case? I believe it would be much simpler if you fully converted all the cross service communication to Cadence. Transfer-websockets service would implement an activity and external writer can start the workflow directly instead of publishing to the Kafka topic.
Good point! To be honest, it did not occur to me but I see what you mean.
It sound like a good material for a new post :-)
I will work on that, stay tuned!