-
Notifications
You must be signed in to change notification settings - Fork 334
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
How to Subscribe for events #288
Comments
For subscribing to events please see, https://github.com/dapr/docs/blob/master/reference/api/pubsub_api.md#required-application-user-code-routes If you are using aspnetcore, then you can use the aspnetcore samples to subscribe to events which adds a route for the topics as well. Dapr building block provides abstraction over multiple components so full fledged functionality is not available, however components allow extending this functionality by providing metadata on requests/response. For specific scenarios in pub/sub building block, please open issue in dapr runtime repo or discuss it in our gitter channel https://gitter.im/Dapr/community |
Thanks for your feedback @amanbha . For example:
|
Subscribed events are discovered by Dapr by calling on to |
Hello @amanbha |
Looking for an example which demonstrates how to subscribe events.
The provided Client sample shows how to publish an event, but there is not way in the DaprClient to receive events.
Especially looking for PUB/SUB concepts like retries, peek-and-lock, peek-and-delete,..
This is all requirement on the concrete component, but do not see anything in the spec related to such concepts.
PUB/SUB building block is definitely extremely important , but common brokers support many integration patterns and features related to them. My question is how to deal with them in dapr.
Publishing an event and receiving t is very basic operation, which will not satisfy most of common enterprise requirements.
Thanks in advance
The text was updated successfully, but these errors were encountered: