In the early days of Microsoft Azure, there was a single Message Queue service; the Azure Storage Queue. This was way back in early 2010, however, soon after that Microsoft introduced another messaging service called Service Bus; then soon after another, and another! Over the years, there have been a few different messaging and message queue services introduced into the Microsoft Azure platform. Each of these messaging services are a little different than each other and offer a pretty wide range of messaging offerings to choose from. This article walks through the primary features of each of the Microsoft Azure messaging services, and will help give you an understanding of when to use each for your own applications and enterprise scenarios. Read More
An Microsoft Azure Service Bus Namespace can certainly be managed through the Azure Management Portal. However easy that is for a user to do manually, it definitely can be useful to create and manage Azure Service Bus Namespaces using other more automated methods. Fortunately, there is support for this using the PowerShell and X-plat CLI SDKs.
Below are examples using both the PowerShell and X-plat CLI (command-line) SDKs to create a new Azure Service Bus Namespace. Read More
Microsoft Azure Service Bus provides an PaaS (Platform as a Service) communications platform built to allow more robust, multi-tenant software systems to be built in the cloud. There are four main feature sets within Azure Service Bus (Queues, Topics, Relays, and Event Hubs) that all offer different communications mediums for use with and between the different tenants of cloud hosted and hybrid (cloud and on-premises) hosted applications.