Book Image

Mastering Cloud Development using Microsoft Azure

By : Roberto Freato, Marco Parenzan
Book Image

Mastering Cloud Development using Microsoft Azure

By: Roberto Freato, Marco Parenzan

Overview of this book

Microsoft Azure is a cloud computing platform that supports many different programming languages, tools, and frameworks, including both Microsoft-specific and third-party software and systems. This book starts by helping you set up a professional development environments in the cloud and integrating them with your local environment to achieve improved efficiency. You will move on to create front-end and back-end services, and then build cross-platform applications using Azure. Next you’ll get to grips with advanced techniques used to analyze usage data and automate billing operations. Following on from that, you will gain knowledge of how you can extend your on-premise solution to the cloud and move data in a pipeline. In a nutshell, this book will show you how to build high-quality, end-to-end services using Microsoft Azure. By the end of this book, you will have the skillset needed to successfully set up, develop, and manage a full-stack Azure infrastructure.
Table of Contents (15 chapters)
Mastering Cloud Development using Microsoft Azure
About the Authors
About the Reviewer

Sending messages with queues

At the time of writing this, managing a Service Bus is possible only from the classic portal:

The common concept at the heart of a service bus is the namespace. Every service needs a public endpoint reachable from the outside. So, the first thing to do with a service bus is assign a name that will be used under the DNS name. There is no standalone way to create a namespace without creating a specific service, such as a queue, relay, topics, notification hub, and EventHub, but it is possible to then create every other service.

So, we need a queue to send commands to act on a basket. We select MESSAGING from the dialog box, type the namespace name in the field, and select the Messaging Tier, between the BASIC and STANDARD ones. The difference between these refers to the capacity to handle a given number of messages. It is always possible to change this during the lifetime of the messaging tier as performances require.


At the time of writing...