Azure Architecture and Design Patterns Workshop

Designing cloud solutions feels very easy, a few clicks on the Azure portal and you can have a running application in cloud on no time. Perhaps it is too easy and, in the rush, we tend to forget the quality of the solution. Workloads on clouds are essentially distributed systems and subject to the vagaries of cloud such as transient faults or unexpected events. Your solution must survive in this environment.

    In this workshop, we will build a cloud solution using .Net Core 3.1 in C# that demonstrates the design patterns for a well-architected Azure application. We will code microservices applications using Azure Serverless and PAAS services as listed below.


    This is a developer-focused workshop and will exclude IAAS solutions including VMs and AKS. Specifically, we will cover how to use Azure PAAS and Serverless services to build highly available, cost-effective, enterprise-quality applications.

    At the end of the workshop, you will learn some patterns, guardrails, technology choices, and best practices for building Azure cloud applications:

    • Azure Services
    • Azure App Services
    • Azure Functions
    • Azure API Management
    • Azure Storage
    • Azure Service Bus
    • Azure Event Hub
    • Azure Cosmos DB
    • Azure SQL
    • Azure Redis
    • Azure KeyVault
    • Azure Monitoring

    Patterns covered:

    • Synchronous integration with APIs and gRPC
    • Asynchronous and Event based integration
    • Transient Fault Handling and Resiliency
    • Scalability (Load Balancing, Autoscaling)
    • Sagas
    • Caching
    • Sharding
    • and More

    Computer Setup:

    • Windows 10 Pro or Mac OSX (I will be on Win 10)
    • Have your own Azure subscription (create a free one https://azure.microsoft.com/free/ )
    • Azure CLI
    • Visual Studio Code and/or Visual Studio 2019
    • Optionally WSL & Docker desktop with Kubernetes
    Programutvikling uses cookies to see how you use our website. We also have embeds from YouTube and Vimeo. How do you feel about that?