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)
Part 1: PaaS and Containers
Part 2: Serverless and Reactive Architecture
Part 3: Storage, Messaging, and Monitoring
Part 4: Performance, Scalability, and Maintainability

Integrating functions with other services

In the last part of this chapter, we will focus a little bit on understanding how Azure Functions integrates with other Azure services. We will look at the available triggers and bindings and try to figure out the best use cases for them along with how they really work. This section is designed in a way that enables you to explore more by yourself—thanks to a common understanding of how Azure Functions works.

The Function file

The way in which the Azure Functions bindings work is that they are compiled into a metadata file, which is generated when your function app is built. This file can be found among your compilation artifacts (try searching for the functions.metadata file). The file structure can be a little bit different depending on the platform used and the actual triggers/outputs, but the generic structure can be presented as follows:

    "name": "HttpTrigger1"...