Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a simple, shared set of architecture standards that Principals can reference in their daily decision-making.
Topics
- Architecture principles: determining what to standardize versus what teams should decide independently
- Decomposition basics: defining boundaries and ownership
- Integration basics: API contracts, versioning, and compatibility
- Messaging overview: comparing Kafka and RabbitMQ, and identifying key areas for standardization
- Data overview: managing ownership and source-of-truth considerations (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 code architecture decisions within large solutions.
Topics
- Structuring large .NET solutions: modules, layering, and boundaries
- Dependency direction and maintaining visible architecture in code
- Shared libraries: understanding when they add value versus when they introduce coupling
- Integration boundaries in code: separation of concerns patterns
- Code architecture “review lenses”: identifying key areas for quick assessment
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Implement a consistent design review approach that leads to clear decisions and shared understanding.
Topics
- Characteristics of a strong Principal-level design review
- 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: effectively ending debates and enabling progress
- 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: Enhance habits related to mentoring, feedback, and alignment with individual contributors.
Topics
- Mentoring versus directing: coaching without taking over ownership
- Providing high-level technical feedback (clear and standards-based)
- Fostering alignment across ICs: practical techniques
- Constructively handling disagreement and resistance
- Simple conversation patterns and reusable scripts for Principals
Requirements
Participants should bring two to three anonymized examples of recurring debates, such as 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.
