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

Avoiding common mistakes and pitfalls

Building a robust and secure cloud storage solution requires careful planning and adherence to best practices. It’s essential not to rush the development process, instead focusing on understanding and circumventing common mistakes. Let’s dive into some typical pitfalls in Azure Blob Storage and how to best avoid them for a smooth and efficient implementation:

  • Storing secrets in plaintext:
    • Mistake: Storing your connection string in plaintext within your application’s source code.
    • Solution: Leverage the power of Azure Key Vault or Azure App Configuration to store and efficiently manage your connection strings. Alternatively, adopt managed identities and Azure Active Directory (AAD) integration to eliminate the need for manual connection string management.
  • Ignoring performance limitations:
    • Mistake: Using a general-purpose Azure Blob Storage account for large-scale data lake workloads. Such storage accounts aren’...