Course Outline
Module 1: Architecture Standards that Scale
Objective: Establish a straightforward, shared set of architecture standards that Principals can reference in their daily decision-making.
Topics
- Architecture principles: Identifying what to standardize versus what teams should decide independently
- Decomposition fundamentals: Defining boundaries and ownership
- Integration fundamentals: API contracts, versioning, and compatibility
- Messaging overview: Kafka vs. RabbitMQ, identifying areas for standardization
- Data management: Ownership and source-of-truth concepts (MongoDB + 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 architectural visibility in code
- Shared libraries: 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 focus on during quick reviews
- Managing exceptions without compromising consistency
Module 3: Design Reviews that Drive Decisions
Objective: Implement a consistent design review process that yields 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: Resolving debates and moving forward effectively
- 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 related to mentoring, feedback, and alignment with individual contributors.
Topics
- Mentoring vs. directing: Coaching without assuming ownership
- Providing high-level technical feedback that is clear and standards-based
- Fostering alignment across ICs: Practical techniques for success
- Constructively handling disagreement and resistance
- Reusable conversation patterns and scripts for Principals
Requirements
Participants are expected to bring 2–3 anonymized examples of recurring debates, such as those concerning system decomposition, integration strategies, 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.
