Course Outline
Module 1: Architecture Standards that Scale
Objective: Agree on a simple, shared set of architecture standards that Principals can reference in their daily decision-making.
Topics
- Architecture principles: distinguishing what needs standardisation from what teams should decide
- Decomposition fundamentals: defining boundaries and ownership
- Integration fundamentals: API contracts, versioning, and compatibility
- Messaging overview: Kafka vs RabbitMQ and areas suitable for standardisation
- Data overview: ownership and source-of-truth thinking (MongoDB + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation (ADR/RFC concepts)
Module 2: Code Architecture in Large .NET Solutions
Objective: Align on practical guidance for code architecture decisions within large-scale solutions.
Topics
- Structuring large .NET solutions: modules, layering, and boundaries
- Dependency direction and maintaining architectural visibility in code
- Shared libraries: identifying when they are beneficial versus when they introduce coupling
- Integration boundaries in code: separation of concerns patterns
- Code architecture "review lenses": key areas to scrutinise quickly
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent design review approach that yields clear decisions and shared understanding.
Topics
- Characteristics of a strong design review at the Principal level
- Review workflow: determining what gets reviewed and when
- Review criteria: focusing on the few aspects that matter most
- Facilitation: keeping senior discussions focused and productive
- Decision closure: techniques for ending debates and moving forward
- Capturing outcomes: documenting decisions and follow-up actions
- Practical review exercise using a short case study (system-level)
Module 4: Influence Without Authority for Principals
Objective: Strengthen habits around mentoring, feedback, and alignment with individual contributors.
Topics
- Mentoring versus directing: coaching without taking ownership
- Providing high-level technical feedback (clear and standards-based)
- Driving alignment across individual contributors: practical techniques
- Constructively handling disagreement and resistance
- Simple conversation patterns and scripts that Principals can reuse
Requirements
Participants should bring 2–3 anonymised examples of recurring debates, such as those concerning system decomposition choices, integration approaches, or code structure rules. Sharing any existing internal standards is optional.
Testimonials (2)
Trainer knowledge, involvement, and rapport
Adam Kuklewski - GE Medical Systems Polska
Course - Technical Architecture and Patterns
I liked the exercises that helped to open the mind and gain new insights into software architecture.
