Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call external micro-service #32

Open
igdmitrov opened this issue Dec 6, 2020 · 1 comment
Open

Call external micro-service #32

igdmitrov opened this issue Dec 6, 2020 · 1 comment

Comments

@igdmitrov
Copy link

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!

@dazinator
Copy link

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:

  1. 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.
  2. Have your worker microservices listen to its activity type message queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants