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

The API Gateway pattern

When developing applications based on complex or large microservices established on multiple client applications, it is recommended to use the API Gateway pattern.

Definition

The API Gateway pattern is an integration pattern for clients that communicate with a system service, designed to provide a single abstraction layer between the underlying services and the customer’s needs. This is the single entry point for all clients. It is similar to the Façade pattern of object-oriented programming (OOP) design, but in this case, it’s part of a distributed system.

The API Gateway pattern is often referred to as Backend for Frontend because its implementation is based on the needs of the client application. The pattern provides a reverse proxy whose purpose is to redirect or route client requests to internal microservices endpoints.

When should you consider using the API Gateway pattern? The following list specifies when it is suitable...