Azure Service Bus
We looked at how to create a web service, how to add functionality around notifications, integration with mobile services, deployment, and more. Now we will shift our focus to the middle tier of the solution architecture. In scalable systems, you would want to decouple direct connections between portions of your application. Just as when you created multi-tiered systems for use on-premises, we will do the same for our architecture in Azure. We want to divide the application components into separate features or areas of concern. By doing so we can create boundaries with low coupling, which leads to less feature overlap and more flexibility.
As such, you don't want to connect the web service directly to the database. There are many reasons for this. What happens if the database is inaccessible? What happens if there is processing that is needed on the incoming data? Azure provides components that we can utilize so that we don't connect components of our application together...
