Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a simple, shared set of architecture standards that Principals can use as a reference in daily decision-making.
Topics
- Architecture principles: identifying what to standardize versus what teams should decide
- Decomposition fundamentals: defining boundaries and ownership
- Integration fundamentals: API contracts, versioning, and compatibility
- Messaging overview: Kafka vs RabbitMQ and areas for standardization
- Data overview: concepts of ownership and source-of-truth (Mongo + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation using ADR/RFC concepts
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: assessing when they add value versus when they introduce coupling
- Integration boundaries in code: applying separation of concerns patterns
- 'Review lenses' for code architecture: key areas to focus on during quick reviews
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent approach to design reviews that yields 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 factors that matter most
- Facilitation techniques: keeping senior discussions focused and productive
- Decision closure: methods to resolve debates and advance
- Capturing outcomes: documenting decisions and follow-up actions
- Practical review exercise using a short system-level case study
Module 4: Influence Without Authority for Principals
Objective: Strengthen habits around mentoring, feedback, and alignment with individual contributors (ICs).
Topics
- Mentoring versus directing: coaching without assuming ownership
- Delivering high-level technical feedback that is clear and standards-based
- Fostering alignment across ICs using practical techniques
- Constructively handling disagreement and resistance
- Reusable conversation patterns and scripts for Principals
Requirements
Participants should come prepared with 2–3 anonymized examples of recurring debates (e.g., system decomposition decisions, integration strategies, or code structure guidelines). Sharing any existing internal standards is optional but encouraged.
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.
