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: 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 (concepts of ADR/RFC)
Module 2: Code Architecture in Large .NET Solutions
Objective: Align on practical guidance for code architecture decisions within large-scale solutions.
Topics
- Structuring large .NET solutions: modules, layering, and boundaries
- Dependency direction and maintaining visible architecture in code
- Shared libraries: benefits versus the risk of coupling
- Integration boundaries in code: patterns for separation of concerns
- Code architecture "review lenses": key elements to look for during quick assessments
- Managing exceptions while maintaining consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent design review approach that results in clear decisions and shared understanding.
Topics
- Characteristics of strong design reviews at the Principal level
- Review workflow: determining what gets reviewed and when
- Review criteria: focusing on the most critical factors
- Facilitation techniques: keeping senior discussions focused and productive
- Decision closure: strategies for ending debates and moving forward
- 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 individual contributors.
Topics
- Mentoring versus directing: coaching without taking ownership
- Giving high-level technical feedback: ensuring clarity and adherence to standards
- Driving alignment across ICs: practical techniques for consensus
- Handling disagreement and resistance constructively
- Reusable conversation patterns and scripts for Principals
Requirements
Participants should bring two to three anonymized examples of recurring debates, such as those regarding system decomposition, integration approaches, or code structure guidelines. 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.
