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

Azure Event Hubs Capture feature

There is one feature of Azure Event Hubs that requires an individual section itself to describe it in depth. Capture is a functionality that allows you to automatically store events using a predefined storage solution (such as Azure Storage or Azure Data Lake) and process them further. Unfortunately, this feature is often misused as its use cases are not so obvious; additionally, the way it works might sometimes be unclear. 

What is an Azure Event Hubs Capture?

In common use cases for Event Hubs, you need a producer and a consumer to fetch data and process it. Let’s consider the following scenario:

Figure 13.18 – Multiple processing flows for Azure Event Hubs

In this scenario, we have two consumers:

  • Consumer 1 for some generic processing
  • Consumer 2 for archiving events

Additionally, we introduced storage for...