dotnet-architecture/messaging

.NET Core Application blocks for message-based communication

messaging's Issues

Suggestions; bi-directional communication and other queues.

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.