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

[Question] How do we handle a situation where consumer and publisher broker address is different? #1058

Closed
ehtesam4m opened this issue Dec 16, 2021 · 3 comments
Labels

Comments

@ehtesam4m
Copy link

I have been looking at this library and it's really awesome. Thanks for the great work. I have two questions.

  1. How do we handle a situation where consumer and publisher broker address is different? For example, If I am consuming from one broker and publishing to another broker.
  2. Can we have multiple publisher and consumer? For example: if we are publishing and consuming from multiple brokers in the same application, is it possible to do it?

P.S: We are using Kafka

@yang-xiaodong
Copy link
Member

Hello,

We currently do not provide direct support for this, but there is a way to achieve it, you can check this comment to get details

#998 (comment)

@ehtesam4m
Copy link
Author

Hi, Thanks for the quick reply. For multi publisher situation, do they use separate "Published" table or the same table? If same, can we configure separate tables? Are there any work around for multi/different broker subscriber?

@yang-xiaodong
Copy link
Member

It depends on your configuration, but I think different tables should be used because they need to be isolated from each other.

For multi-instance consumers, you can customize IConsumerServiceSelector to get different instances To its corresponding consumers and exclude subscribers from other instances, all these behaviors require you to have sufficient knowledge of this library and fully test it

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

No branches or pull requests

2 participants