Testing Software Architecture
summary
Shows concrete tests that validate architecture not features: implement fitness functions that run in production or CI to catch structural decay, using Kafka for observability, measure queue depth, mean time to start (from Kubernetes), and response-time vs concurrency trends to prove support for 200,000 students. Demonstrates triggered vs continuous tradeoffs, gives code-level structural checks using Arc unit / Arcunit Nets / net Arc test and tools like sonar graph to enforce layering and prevent tight coupling.
AI-written summary · about
chapters (8)
- 0:00The problem of architectural decay
- 2:17Defining architectural testing
- 5:50Operational characteristics
- 11:52Fitness functions for measurement
- 18:05Triggered vs. continuous testing
- 25:41Implementing integrity tests
- 34:02Elasticity and throughput analysis
- 43:20Structural integrity constraints
related talks
51mTesting Software Architecture
40mTesting Software Architecture
44mTesting Software Architecture
43mTesting Software Architectures
53mTest architecture is a real thing
01h 34mThe Intersection of Architecture and Implementation
58m4 Key Trends Towards Better Software Architecture
01h 15mHow to measure your architecture