ATAM-risk | How to determine architecture risks
RisksHere are exampples of Risks :
The software is not maintainable. User interface and business logic change need code change and deployment. It limits the capability to do a/b testing.
Upgrade to software can’t be done during peak hours (11 AM-2PM PST) as all servers serving the traffic.
The decision to copy data to reporting at interval of 24 hours means reporting business will see report with 24 hours delay.
What is Non Risks
Here are examples of Non-RisksAs both Data center can take serve full traffic including peak hour, it means a failure/disaster in one DC can be handled.
For Targetting it is okay to use yesterday data instead of real time data.
10-Risks 11-Non-Risks 2-why-to-use-atam 3-What-does-ATAM-discover 4-ATAM-Cost-and-benefits 5-ATAM-roles 6-ATAM-Steps-Summary 7-ATAM-Steps 8-Tradeoffs 9-Sensitivity-Points