Completed
Forces design in a way that is not restrictive
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
How to Design for Multi-Cloud Deployment - Best Practices and Considerations
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Redundancy & Availability
- 3 Latency, Geographic Considerations
- 4 Cost & Feature Options Best possible cloud for each workload Cloud can become platform
- 5 Forces design in a way that is not restrictive
- 6 Choosing cloud providers
- 7 Don't design for a specific cloud Lock-in dangers as mentioned Platform restrictions -e.g., Kubernetes
- 8 Plan your architecture Locations requirements, etc.
- 9 Ensure your requirements are met Databases Egress data fees / structure Staff abilities and training Regulatory requirements
- 10 Investigate commercials Contracts and commercials Support and SLA Reliability and performance guarantees
- 11 Consider 2x clouds or 1 cloud + X Hybrid cloud, hybrid platforms Custom datacenters App-based services and deployments
- 12 Consider your architecture
- 13 Try to automate deployments
- 14 Utilize auto-scaling functions Don't pay for 100% high availability Ensure AWS outage causes scaling in GCP, etc.
- 15 Route traffic with GSLB Global Server Load Balancing Intelligent DNS server Allows for test deployments, weighting
- 16 Centralized Monitoring
- 17 3. Cloud For Layer 4 Solutions Handle layer 4 security at the cloud level Security groups, etc.
- 18 How Snapt does it?
