Before choosing a cloud service, clarify what the system actually needs to guarantee. A useful diagram expresses constraints and decisions, not just a collection of services.
1. Define the requirement
A demonstration application and a payment service do not share the same requirements. Define expected availability, the data to protect and the acceptable recovery time. These criteria guide the architecture.
2. Separate responsibilities
Separate the public entry point, application logic and data. A database generally does not need to be directly reachable from the Internet. The application should access it with limited permissions.
3. Identify failure points
Two servers in the same failure domain do not guarantee resilience. Ask what happens if an availability zone, a dependency or a connection becomes unavailable. A backup must also be restorable.
Internet
│
Load balancer
├── Application — zone A
└── Application — zone B
│
Private database
│
Tested backup policyYour turn to build
Draw a three-tier web application. Mark what is public, what is private and the point whose failure would stop the service. Then propose an improvement and its cost.
Your discovery progress is saved on this device. You can clear it from My learning.