Describe the workload and consequence of failure
List the application users traffic pattern data types integrations processing needs and expected growth. Explain what the business experiences when the service is unavailable slow or loses recent information. These facts shape architecture more than a provider brand.
Separate public website needs from internal systems transaction processing background work media and analytics. One organization can use different hosting models for different workloads when the boundaries and responsibilities are clear.
- Users traffic and regions
- Data and integration needs
- Business impact of failure
