1 / 30

Architecting Highly Resilient Applications on Azure - A Comprehensive Guide

Learn how to architect resilient apps on Azure - from modeling to building to running. Explore HA, DR, responsiveness, and performance considerations. Discover key patterns and best practices for application resilience.

cowles
Download Presentation

Architecting Highly Resilient Applications on Azure - A Comprehensive Guide

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecting highly resilient applications on Azure Mahesh Krishnan ARC427

  2. Agenda What do we want to achieve? What comes out of the box? Architecting resilient apps: Modelling Building Running A sample implementation

  3. What do we want to achieve? High Availability (HA) Is your app available all (or most of) the time? Disaster Recovery (DR) What happens when something really bad happens? How do you recover from disaster? Responsiveness How does your app react to user (or system) interaction? Performance How quickly do things happen?

  4. What comes out of the box?

  5. Architecting for resilience

  6. Modelling your application

  7. Workload modelling Understand and decompose your application based on the workload of your application Considerations: Bounded contexts Explicit dependencies Data partitioning and data locality Divide first, then multiply

  8. Lifecycle modelling Model the load lifecycle of the application and its behaviour when operational

  9. Statistics workload –An example

  10. Liveworkload –An example

  11. Modelling Availability Establish SLAs based on Workload and Lifecycle model

  12. Modelling for failure Embrace failure: But first, identify and analyse their effects Considerations: Capability failures – Application logic, Transaction failures Connectivity failures – Database/Storage, Upstream services Capacity failures – Storage, Network Configuration failures – Security (roles), Certificates, metadata

  13. Building your application

  14. Patterns for building the application Resiliency patterns Redundancy patterns Recovery patterns

  15. Resiliency pattern – Async everything Application

  16. Resiliency patterns for handling errors

  17. Resiliency pattern – Circuit breakers Plan A(default) CB Route some traffic… Closed Open Half Open Plan B

  18. Redundancy patterns

  19. Recovery patterns

  20. Running your application

  21. Considerations

  22. A Sample implementation

  23. Azure Traffic Manager DC 1 DC 2 Web Apps & Web Jobs Web Apps & Web Jobs Live Replication

  24. Demo

  25. Key takeaways… Do not avoid failure. Embrace it! Model your workload, lifecycle and your failures Apply patterns for Resilience, Redundancy and Recovery Asynchrony, Timeouts, Circuit breakers, Cross DC replication,Backup/restore, etc. Automate, Monitor and Measure

  26. Complete your session evaluation on My Ignite for your chance to win one of many daily prizes.

  27. Continue your Ignite learning path Visit Microsoft Virtual Academy for free online training visit https://www.microsoftvirtualacademy.com Visit Channel 9 to access a wide range of Microsoft training and event recordings https://channel9.msdn.com/ Head to the TechNet Eval Centre to download trials of the latest Microsoft products http://Microsoft.com/en-us/evalcenter/

More Related