Optimizing Task Distribution and Scaling with Conductor #205
Unanswered
idan-dagan-imagenai
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am currently using SQS and KEDA to scale my microservices on Kubernetes. As my workflow becomes increasingly complex, I've considered using an orchestration system like Conductor. However, I am unsure about how to scale my deployment horizontally.
My questions are:
Should I continue using SQS/SNS, or can I rely entirely on Conductor's queue system if I decide to migrate?
How do I scale my task workers horizontally? For example, if I have a workflow with several tasks triggered ten times, I want to ensure that not all tasks run on the same pod. How can I achieve horizontal scaling of my pods?
I hope my questions are clear. Thanks for your help!
Beta Was this translation helpful? Give feedback.
All reactions