You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I really appreciate your work and you have a great project.
I read the documentation and I can't find a solution on how to call external micro-service (worker) from the conductor. Yes, I can check "my-activity" but if I have a lot of workers? In this case I think it was a performance issue.
I would like to understand the correct architecture before diving in.
Thank you in advance!
The text was updated successfully, but these errors were encountered:
I just stumbled accross this project and read all the docs. My interpretation of this is to just use an activity. What is the issue with the activity mechanism that you see as problematic?
The one issue I don't like is when you might have say a huge number of microservice instances all polling the conductor api. However this can be elimated thus:
Create a single service that polls the conductor api and when it receives a message, place that message on a queue named for the activity type.
Have your worker microservices listen to its activity type message queue.
Hello,
I really appreciate your work and you have a great project.
I read the documentation and I can't find a solution on how to call external micro-service (worker) from the conductor. Yes, I can check "my-activity" but if I have a lot of workers? In this case I think it was a performance issue.
I would like to understand the correct architecture before diving in.
Thank you in advance!
The text was updated successfully, but these errors were encountered: