-
Notifications
You must be signed in to change notification settings - Fork 68
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
Comments
I assume you're referring to 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? |
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. |
How would you configure which events go to which topic (and partition)? |
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". |
Yes, I consider this essential too. This will open up a lot of flexibility for clients in an event-driven architecture. |
According to documentation RIG supports only one Kafka topic to publish messages. It would be good idea to support more topics to publish events.
The text was updated successfully, but these errors were encountered: