Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a simple, unified 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
- Decomposition fundamentals: defining boundaries and ownership
- Integration fundamentals: API contracts, versioning, and compatibility
- Messaging overview: Kafka vs RabbitMQ and areas suitable for standardization
- Data overview: approaches to ownership and source-of-truth thinking (Mongo + SQL Server)
- Common architectural anti-patterns found 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 visibility of architecture in the codebase
- Shared libraries: assessing when they add value versus when they introduce 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: Create a consistent design review process that yields clear decisions and shared understanding.
Topics
- Characteristics of a strong Principal-level design review
- Review workflow: identifying what gets reviewed and when
- Review criteria: focusing on the most critical factors
- Facilitation techniques for keeping senior discussions focused and productive
- Decision closure: strategies for resolving debates and advancing
- 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: Enhance habits related to mentoring, feedback, and alignment with individual contributors.
Topics
- Mentoring versus directing: coaching without assuming ownership
- Delivering high-level technical feedback that is clear and standards-based
- Driving alignment among ICs: practical techniques
- Constructively handling disagreement and resistance
- Simple conversation patterns and scripts that Principals can reuse
Requirements
Participants are expected to bring 2–3 anonymized examples of recurring debates, such as those regarding system decomposition choices, integration approaches, or code structure rules. Sharing any existing internal standards is optional.
Testimonials (3)
Trainer knowledge, involvement, and rapport
Adam Kuklewski - GE Medical Systems Polska
Course - Technical Architecture and Patterns
The clarity with which the topics were explained
CHRISTIAN ANDRES ALCANTAR NOYOLA - Seguros El Potosi
Course - Architecture for Developers
Machine Translated
I liked the exercises that helped to open the mind and gain new insights into software architecture.
