Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a simple, shared set of architecture standards that Principals can reference in daily decisions.
Topics
- Architecture principles: distinguishing what to standardize versus what teams decide
- Decomposition basics: defining boundaries and ownership
- Integration basics: API contracts, versioning, and compatibility
- Messaging overview: Kafka vs RabbitMQ, and what to standardize
- Data overview: ownership and source-of-truth considerations (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 solutions.
Topics
- Structuring large .NET solutions: modules, layering, and boundaries
- Dependency direction and maintaining visible architecture in code
- Shared libraries: when they help versus when they create coupling
- Integration boundaries in code: separation of concerns patterns
- Code architecture 'review lenses': key aspects to focus on 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
- Characteristics of a strong design review at the Principal level
- Review workflow: determining what gets reviewed and when
- Review criteria: focusing on the few elements that matter most
- Facilitation: keeping senior discussions focused and productive
- Decision closure: strategies 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 mentoring, feedback, and alignment habits with ICs.
Topics
- Mentoring versus directing: coaching without taking ownership
- Providing high-level technical feedback (clear and standards-based)
- Driving alignment across ICs: practical techniques
- Handling disagreement and resistance constructively
- Simple conversation patterns and scripts Principals can reuse
Requirements
Participants should bring 2–3 anonymized examples of recurring debates (covering system decomposition choices, integration approaches, and 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.
