Book Image

A Developer's Guide to Building Resilient Cloud Applications with Azure

By : Hamida Rebai Trabelsi
Book Image

A Developer's Guide to Building Resilient Cloud Applications with Azure

By: Hamida Rebai Trabelsi

Overview of this book

To deliver software at a faster rate and reduced costs, companies with stable legacy systems and growing data volumes are trying to modernize their applications and accelerate innovation, but this is no easy matter. A Developer’s Guide to Building Resilient Cloud Applications with Azure helps you overcome these application modernization challenges to build secure and reliable cloud-based applications on Azure and connect them to databases with the help of easy-to-follow examples. The book begins with a basic definition of serverless and event-driven architecture and Database-as-a-Service, before moving on to an exploration of the different services in Azure, namely Azure API Management using the gateway pattern, event-driven architecture, Event Grid, Azure Event Hubs, Azure message queues, FaaS using Azure Functions, and the database-oriented cloud. Throughout the chapters, you’ll learn about creating, importing, and managing APIs and Service Fabric in Azure, and discover how to ensure continuous integration and deployment in Azure to fully automate the software delivery process, that is, the build and release process. By the end of this book, you’ll be able to build and deploy cloud-oriented applications using APIs, serverless, Service Fabric, Azure Functions, and Event Grid technologies.
Table of Contents (18 chapters)
1
Part 1: Building Cloud-Oriented Apps Using Patterns and Technologies
5
Part 2: Connecting Your Application with Azure Databases
13
Part 3: Ensuring Continuous Integration and Continuous Container Deployment on Azure

Securing the API

When publishing APIs via API Management, access to these APIs is secured by using subscription keys. Developers must include a valid subscription key in HTTP requests when calling an API; otherwise, these calls will be rejected by the API Management gateway. However, the transmission to the backend is not ensured.

If a developer wants to consume published APIs, a subscription is required. Developers who want to consume the published APIs must include a valid subscription key in HTTP requests when calling those APIs. But the calls can be rejected immediately by the API Management gateway or will not be forwarded to the backend services without a valid subscription key. They can get a subscription without approval from API publishers, although API publishers can even create subscriptions directly for API consumers.

Several API access security mechanisms are supported for Azure API Management Service, such as OAuth 2.0, client certificates, and IP allow lists.

...