Architecting for Application Requirements
A look at understanding application requirements then architecting at both the infrastructure and application level to meet those requirements.
A look at understanding application requirements then architecting at both the infrastructure and application level to meet those requirements.
In this Video
0:00 - Introduction
0:50 - Understanding the application requirements
6:15 - What can fail?
9:50 - Elements of the architecture
14:25 - Service SLAs
19:32 - Introducing bulkhead thinking
22:38 - Using the right SLA
23:45 - Combining multiple services and the composite SLA
27:38 - Combining Azure services
29:53 - Improving the SLA
34:55 - The balancer and other issues
37:31 - Other resiliency options and using a cache
40:50 - Helping with application architecture
41:45 - Scales of resiliency in infrastructure
45:35 - Improvements to the application
47:00 - Bulkheads in the application architecture
49:40 - Alternate paths and database considerations
52:40 - Different pools
54:39 - Decoupling
56:29 - Caching detail
1:00:35 - Circuit breaking and leaking buckets
1:06:10 - Other best practices
1:09:48 - Summary
Using business metrics to design resilient Azure applications
Are availability targets such as Service Level Agreements (SLAs), Service Level Indicators (SLIs), and Service Level Objectives (SLOs) defined for the application or key scenarios?