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

Debugging complex API workflows

The more we complicate the topology of the API workflow, the more complex the debugging activity around it will be. Now imagine this scenario:

  1. The user calls

  2. v1 in the URI determines that the backend URI,, has to be called.

  3. APIM performs some activities (due to the policies) and calls the backend service.

  4. After that, it calls another service to compose the response and returns it to the client.

Now, suppose that the client has an error code and we need to determine where it occurred:

  • Has it happened on the V1 side?

  • Has it happened in the Utility service?

  • Has it happened on the APIM side (due to policy execution errors)?

The first instrument we can use to diagnose what happened is the API inspector of APIM, a feature that traces calls in order to troubleshoot the pipeline.

If we can replicate the error conditions (hopefully), then we can call the APIM endpoint, specifiying an additional header...