Analyzing Architectural Risk
summary
Analyzes a concrete web testing system "make the grade" that must handle 20 to 120,000 concurrent students and guarantee no lost answers. Identifies high-risk areas (signin, test taker, queue, autograder), shows mitigation tactics like caching, sharding, autoscaling and federating queues, and suggests persistent brokers such as Kafka. Proposes collaborative riskstorming to quantify impact/likelihood and automated architectural fitness functions (checksums, error streams, trend/threshold alerts) to measure whether fixes actually reduce risk.
AI-written summary · about
chapters (7)
- 0:00Introduction to architectural risk
- 7:53Determining risk dimensions
- 16:35Identifying architectural risks
- 29:29Mitigating identified risks
- 36:38Measuring risk with fitness functions
- 47:16Continuous risk assessment process
- 49:46Closing and Q&A
related talks
51mTesting Software Architecture
58mTesting Software Architecture
55mArchitectural Risk Assessments
01h 15mHow to measure your architecture
28mAn Open Source Architecture for Modernizing Market Risk Managem...
01mListening to the design pressures
35mTell me why - About the purpose of architectural work
50mTest Intelligence for Architects
