You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2021. It is now read-only.
Thanks for putting this together. I just had a few suggestions for things that would be nice to see here.
Firstly most message queues have some sample code for basic publishing. One thing that always seems to be missing is bi-directional communication, especially if you are doing a query/response model. I know that some would argue that web services are more suitable for that for that use case but sometimes you want durable and/or disconnected communication. It'd be really good to show some solid patterns for doing that (especially handling response delivery to the correct node when there are multiple publishers and subscribers).
Other than that it'd be nice to see examples here for the new .Net Standard SDKs for Event Hubs and Service Bus (although the later is in preview still).
Thanks again.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thanks for putting this together. I just had a few suggestions for things that would be nice to see here.
Firstly most message queues have some sample code for basic publishing. One thing that always seems to be missing is bi-directional communication, especially if you are doing a query/response model. I know that some would argue that web services are more suitable for that for that use case but sometimes you want durable and/or disconnected communication. It'd be really good to show some solid patterns for doing that (especially handling response delivery to the correct node when there are multiple publishers and subscribers).
Other than that it'd be nice to see examples here for the new .Net Standard SDKs for Event Hubs and Service Bus (although the later is in preview still).
Thanks again.
The text was updated successfully, but these errors were encountered: