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

Multiple Kafka topics for publish events #229

Closed
LudovitVarga opened this issue Jul 5, 2019 · 5 comments · Fixed by #263
Closed

Multiple Kafka topics for publish events #229

LudovitVarga opened this issue Jul 5, 2019 · 5 comments · Fixed by #263
Assignees
Milestone

Comments

@LudovitVarga
Copy link

According to documentation RIG supports only one Kafka topic to publish messages. It would be good idea to support more topics to publish events.

@kevinbader
Copy link
Contributor

I assume you're referring to PROXY_KAFKA_REQUEST_TOPIC.

Currently, RIG supports only one topic because a frontend (or external client) is not supposed to know anything about the topics used by the backend and therefore cannot select a topic through the request it sends. Could you please elaborate on the use case you have in mind?

@LudovitVarga
Copy link
Author

frontend (or external client) is not supposed to know anything about the topics used by the backend

I agree and that is why we have proxies that are aware of this information. If RIG can act as proxy than why RIG can't have this information about different topics? Currently you define in configuration, url that acts as endpoint to publish messages to Kafka. So why you can't provide multiple endpoints for multiple topics? For frontend is this single entry point, same as in case you have http proxy.

@kevinbader
Copy link
Contributor

How would you configure which events go to which topic (and partition)?

@LudovitVarga
Copy link
Author

Partition can be defined same way as in current solution. Topic can be specified as new parameter in json configuration of endpoints where now you have parameter "target=kafka".

@shafqatevo
Copy link

Yes, I consider this essential too. This will open up a lot of flexibility for clients in an event-driven architecture.

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

Successfully merging a pull request may close this issue.

4 participants