| marp | theme | class | paginate | style | backgroundColor | foregroundColor | backgroundImage |
|---|---|---|---|---|---|---|---|
true |
default |
invert |
true |
img[alt~="center"] {
display: block;
margin: 0 auto;
}
|
- Resiliency
- ability of system to recover from failure and continue to function
- Availability
- whether your users can access your workload when they need to
- percentage uptime
Choosing and confugring the right building blocks and making sure the application understands that its living in the cloud.
- Cloud applications must be designed to expect occasional failures and recover from them.
- Instead of trying to prevent failures altogether, the goal is to minimize the effects of a single failing component.
- Define and test availability and recovery targets and build them into your application
- BCDR Strategy
- SLA, SLO, RPO & RTO
- Design applications to be resistant to failures
- Tactical & strategic
- Recover from errors & automatically recover from failure
- Design resilience to respond to outages
- e.g. through redundancy
- Plan for disaster recovery
- Use fault isolation to protect your workload
- Use Availability Zones where applicable to improve reliability and optimize costs.
- Identify possible failure points in the system with failure mode analysis
- Eliminate all single point of failure.
- Design for scalability
- Backup Data
- Use the native resiliency capabilities of PaaS to support overall application reliability
- Use zone-aware services
- Test recovery procedures
- Test regularly
- Test as part of each major change
- Automate as much as possible
- Test for resiliency
- Design a backup strategy and test it
- Design a disaster recovery strategy and test it
- Codify steps to failover and fallback abnd test it
- Plan for regional failures
- Perform chaos testing by injecting faults and apply chaos principles continuously
- Monitor and measure application health
-
Managing costs to maximize the value delivered.
-
Culture of cost-awareness
- Capture clear requirements
- Estimate the initial cost
- Price Calculator, TCO Calculator, Azure Migrate, AWS Cost Explorer
- Define policies for the cost constraints defined by the organization
- Identify shared assets
- Plan a governance strategy
- Check the cost of resources in various Azure geographic region
- Choose a subscription that is appropriate for the workload
- Choose the right resources to handle the performance
- Compare consumption-based pricing with pre-provisioned cost
- Use proof-of-concept deployments
- Choose managed services when possible
- Gather cost data from diverse sources to create reports
- Use resource tag policies to build reports
- Respond to alerts and have a response plan according to the constraints
- Revise budgets
- Adopt both proactive and reactive approaches for cost reviews
- Analyze the cost at all scopes
- Detect anomalies
- Use Visualization tools to analyze cost information
Cost has a direct correlation with reliability.
If the cost of high availability exceeds the cost of downtime, you can save by using Azure platform-managed replication and recover data from the backup storage.