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 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: Kafka vs RabbitMQ and aspects that require standardization
- Data overview: thinking about ownership and source-of-truth (Mongo + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation (concepts such as 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 architectural visibility in code
- Shared libraries: when they add value versus when they create coupling
- Integration boundaries in code: separation of concerns patterns
- 'Review lenses' for code architecture: what to look for quickly
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent design review approach that results in clear decisions and shared understanding.
Topics
- What constitutes a strong design review at the Principal level
- Review workflow: what gets reviewed and when
- Review criteria: focusing on the few aspects that matter most
- Facilitation: keeping senior discussions focused and productive
- Decision closure: how to end debates and move 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 around mentoring, feedback, and alignment with individual contributors.
Topics
- Mentoring vs directing: coaching without taking ownership
- Giving high-level technical feedback (clear and standards-based)
- Driving alignment across ICs: practical techniques
- Handling disagreement and resistance constructively
- Simple conversation patterns and scripts that Principals can reuse
Requirements
Participants should bring 2–3 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.
