Book Image

Azure for Developers. - Second Edition

By : Kamil Mrzygłód
5 (1)
Book Image

Azure for Developers. - Second Edition

5 (1)
By: Kamil Mrzygłód

Overview of this book

Microsoft Azure is currently one of the fastest growing public cloud service providers thanks to its sophisticated set of services for building fault-tolerant and scalable cloud-based applications. This second edition of Azure for Developers will take you on a journey through the various PaaS services available in Azure, including Azure App Service, Azure Functions, and Azure SQL Databases, showing you how to build a complete and reliable system with ease. Throughout the book, you’ll discover ways to enhance your skills when building cloud-based solutions leveraging different SQL/NoSQL databases, serverless and messaging components, containerized solutions, and even search engines such as Azure Cognitive Search. That’s not all!! The book also covers more advanced scenarios such as scalability best practices, serving static content with Azure CDN, and distributing loads with Azure Traffic Manager, Azure Application Gateway, and Azure Front Door. By the end of this Azure book, you’ll be able to build modern applications on the Azure cloud using the most popular and promising technologies to make your solutions reliable, stable, and efficient.
Table of Contents (32 chapters)
1
Part 1: PaaS and Containers
8
Part 2: Serverless and Reactive Architecture
14
Part 3: Storage, Messaging, and Monitoring
22
Part 4: Performance, Scalability, and Maintainability

The main concepts of Azure API Management

Before we get started with Azure API Management as a service, let’s briefly discuss the purpose of this service. In many information technology (IT) systems, there are various APIs that are often built by different teams using different technologies. Each of these APIs must authenticate requests, track them, and possibly implement a sophisticated way to handle retries, caching, or thresholding. While doing all these independently may not seem like a bad idea, in most scenarios, it will be considered a bad practice.

The reason for avoiding doing such operations individually in each service is simple–we want to avoid duplication. It is not only relevant for the code base—where architecture is designed, the overall aim is to reuse available components if possible. If there is a way to centralize mentioned features, we should always leverage it.

This is where services such as Azure API Management come into play—...