Course Outline
Module 1: Architecture Standards that Scale
Objective: Agree on a simple, shared set of architecture standards that Principals can reference in daily decisions.
Topics
- Architecture principles: determining what to standardize versus what teams should decide
- Decomposition basics: defining boundaries and ownership
- Integration basics: API contracts, versioning, and compatibility
- Messaging overview: comparing Kafka and RabbitMQ, identifying areas for standardization
- Data overview: concepts of ownership and source-of-truth (MongoDB + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation (concepts of ADR/RFC)
Module 2: Code Architecture in Large .NET Solutions
Objective: Align on practical guidance for making code architecture decisions within large solutions.
Topics
- Structuring large .NET solutions: modules, layering, and boundaries
- Dependency direction and maintaining architectural visibility in code
- Shared libraries: understanding when they add value versus when they create coupling
- Integration boundaries in code: patterns for separation of concerns
- Code architecture "review lenses": key areas to inspect quickly
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent design review approach that yields 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 factors that matter most
- Facilitation: keeping senior discussions focused and productive
- Decision closure: strategies for ending debates and moving forward
- Capturing outcomes: documenting decisions and follow-up actions
- Practice review using a short case study (system-level)
Module 4: Influence Without Authority for Principals
Objective: Strengthen habits related to mentoring, feedback, and alignment with individual contributors.
Topics
- Mentoring versus directing: coaching without taking ownership
- Providing high-level technical feedback that is clear and standards-based
- Driving alignment across individual contributors using practical techniques
- Constructively handling disagreement and resistance
- Simple conversation patterns and scripts that Principals can reuse
Requirements
Participants should bring two to three anonymized examples of recurring debates, such as decisions regarding system decomposition, 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.
