Book Image

A Developer's Guide to .NET in Azure

By : Anuraj Parameswaran, Tamir Al Balkhi
Book Image

A Developer's Guide to .NET in Azure

By: Anuraj Parameswaran, Tamir Al Balkhi

Overview of this book

A Developer’s Guide to .NET in Azure helps you embark on a transformative journey through Microsoft Azure that is tailored to .NET developers. This book is a curated compendium that’ll enable you to master the creation of resilient, scalable, and highly available applications. The book is divided into four parts, with Part 1 demystifying Azure for you and emphasizing the portal's utility and seamless integration. The chapters in this section help you configure your workspace for optimal Azure synergy. You’ll then move on to Part 2, where you’ll explore serverless computing, microservices, containerization, Dapr, and Azure Kubernetes Service for scalability, and build pragmatic, cost-effective applications using Azure Functions and Container apps. Part 3 delves into data and storage, showing you how to utilize Azure Blob Storage for unstructured data, Azure SQL Database for structured data, and Azure Cosmos DB for document-oriented data. The final part teaches you about messaging and security, utilizing Azure App Configuration, Event Hubs, Service Bus, Key Vault, and Azure AD B2C for robust, secure applications. By the end of this book, you’ll have mastered Azure's responsive infrastructure for exceptional applications.
Table of Contents (20 chapters)
1
Part 1: An Introduction to Your Environment
3
Part 2: Serverless and Microservices
8
Part 3: Data and Storage
12
Part 4: Messaging Mechanisms and Security

Event storage and retention

Azure Event Hubs is primarily a streaming platform designed to handle real-time data, but it also features event storage capabilities and configurable retention policies.

When events are sent to an Event Hub, they are stored for a configured period. By default, the retention period is one day, but this can be set to a maximum of seven days in a standard tier Event Hubs namespace or longer with a dedicated tier.

It’s crucial to note that Event Hubs follows a log-based storage system. This means once an event is written, it can’t be changed or deleted until the retention period elapses. Also, events are read in the order they were added to the partition, following a First In, First Out (FIFO) model. In addition to its real-time data streaming capabilities, Azure Event Hubs offers essential features that ensure data reliability, fault tolerance, and scalability. Let’s explore how Azure Event Hubs handles larger retention periods,...