Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a simple, shared set of architecture standards that Principals can reference in their daily decisions.
Topics
- Architecture principles: distinguishing between what to standardize and what teams should decide
- Decomposition basics: defining boundaries and ownership
- Integration basics: API contracts, versioning, and compatibility
- Messaging overview: comparing Kafka and RabbitMQ, and identifying standardization opportunities
- Data overview: focusing on ownership and source-of-truth concepts (MongoDB + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation (concepts such as ADR and 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: managing modules, layering, and boundaries
- Dependency direction and maintaining visible architecture in code
- Shared libraries: balancing benefits against coupling risks
- Integration boundaries in code: separation of concerns patterns
- Code architecture “review lenses”: key areas to scrutinize 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 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: methods to conclude debates and advance
- 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 related to mentoring, feedback, and alignment with ICs.
Topics
- Mentoring versus directing: coaching without assuming ownership
- Delivering high-level technical feedback (clear and standards-based)
- Driving alignment across ICs: practical techniques
- Constructively handling disagreement and resistance
- Simple conversation patterns and scripts reusable by Principals
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.
