Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a simple, shared set of architecture standards that Principals can reference in daily decision-making.
Topics
- Architecture principles: distinguishing 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 standardization guidelines
- Data overview: ownership and source-of-truth concepts (Mongo + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation (ADR/RFC concepts)
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 architectural visibility in code
- Shared libraries: understanding when they add value versus creating coupling
- Integration boundaries in code: patterns for separation of concerns
- Code architecture 'review lenses': key areas to inspect quickly
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent design review approach 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 most critical factors
- Facilitation techniques: keeping senior discussions focused and productive
- Decision closure: resolving debates and moving 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 (ICs).
Topics
- Mentoring vs. directing: coaching without taking ownership
- Providing high-level technical feedback that is clear and standards-based
- Driving alignment across ICs: practical techniques
- Constructively handling disagreement and resistance
- Simple conversation patterns and scripts for Principals to reuse
Requirements
Participants should bring 2–3 anonymized examples of recurring debates (e.g., system decomposition choices, integration approach, 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.
