Sending message from Azure Functions to NServiceBus.
The question I was (poorly) trying to communicate was whether newer versions of the SDK could possibly be affecting NServiceBus working with Azure correctly, specifically around this issue of topics not being created. I would assume that new SDKs probably mean new binaries deployed to the Azure infrastructure, so is it possible we're dealing with a versioning issue?As to which framework to use, there's Nimbus and NServiceBus and possibly others. NServiceBus is a commercial product which comes with extensive documentation, devops and debugging and visualization utilities and additional paid support should you need it. Here's how you get an NServiceBus endpoint up and running with Azure ServiceBus.NServicebus is a library that embeds in your process, it does not need it's own service to run in. It can be embedded in both stateless and stateful services. If you use Azure Service Bus as a transport between simple processing code than it may not need to store state at all (you can opt for the in memory persistence procider). If you need.
The Issue. My worker built upon NServiceBus was not able to subscribe to messages published via Azure Function. I could see message in the message queue, but for some reason my CommandHandler on the worker could not handle the message. Root Cause of the issue. To invoke the correct message handler NServiceBus needs to map the transport message to a message type.Based on state of the art patterns from SOA and proven object-oriented practices, NServiceBus enables parallel service layer development, version tolerant message schemas, as well as fluent business-process unit testing. Speaker: Jimmy Pelletier is an NServiceBus trainer, consultant and organiser of the Alt.Net user group in Melbourne.
Azure Service Bus has two entities, Queues and Topics. In my previous post, I explained Queues and in this post, I will attempt to give a overview of Topics.Consider a scenario where you are shopping for TV packages from WISHTV provider.
