Book Image

Azure for Developers. - Second Edition

By : Kamil Mrzygłód
Book Image

Azure for Developers. - Second Edition

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

Using different schemas in Event Grid

When creating an Event Grid instance, you have the option to choose which event schema will be used for your system:

Figure 11.12 – Choosing between different event schemas for Event Grid

Depending on your requirement, one of the preceding options might fit better with your apps. While there are no strategic differences in the supported schemas, the choice made when provisioning an instance of Event Grid will impact how other services integrate with it.

Event Grid schema

When using the default schema, you will expect that each event uses the following properties when sending data:

[
  {
    “topic”: string,
    “subject”: string,
    “id”: string,
    “eventType”: string,
    “eventTime”: string,
    “...