Course Outline
Module 1: Scalable Architecture Standards
Goal: Establish a simple, shared set of architecture standards that Principals can reference for day-to-day decision-making.
Key Topics
- Architectural principles: Distinguishing between what should be standardized and what is left to team discretion
- Foundations of decomposition: Defining system boundaries and ownership
- Integration fundamentals: Managing API contracts, versioning, and compatibility
- Messaging overview: Comparing Kafka and RabbitMQ, and identifying areas for standardization
- Data considerations: Perspectives on ownership and source-of-truth models (Mongo and SQL Server)
- Common architectural anti-patterns observed in high-scale systems
- Lightweight decision documentation (introducing ADR/RFC concepts)
Module 2: Code Architecture in Large-Scale .NET Solutions
Goal: Align on practical guidelines for making code architecture decisions within large-scale solutions.
Key Topics
- Organizing large .NET solutions: Modules, layering, and boundary definitions
- Managing dependency direction and maintaining architectural visibility within the codebase
- Shared libraries: Assessing when they provide benefits versus when they introduce coupling
- Code integration boundaries: Applying separation of concerns patterns
- Code architecture 'review lenses': Identifying key elements to check quickly
- Exception management that maintains system consistency
Module 3: Design Reviews that Drive Decisions
Goal: Implement a consistent design review process that yields clear decisions and shared understanding.
Key Topics
- Characteristics of effective Principal-level design reviews
- Review workflow: Determining what gets reviewed and at which stage
- Review criteria: Focusing on the most critical factors
- Facilitation: Keeping discussions among senior stakeholders focused and productive
- Decision closure: Techniques for resolving debates and progressing forward
- Documenting outcomes: Recording decisions and defining follow-up actions
- Practical exercise: Conducting a review using a brief system-level case study
Module 4: Exercising Influence Without Authority for Principals
Goal: Enhance mentoring, feedback, and alignment practices with individual contributors.
Key Topics
- Mentoring versus directing: Coaching without assuming ownership of tasks
- Providing high-level technical feedback that is clear and aligned with standards
- Driving alignment across individual contributors: Practical strategies
- Constructively handling disagreement and resistance
- Reusable conversation patterns and scripts for Principals
Requirements
Attendees are requested to prepare 2–3 anonymized instances of recurring technical debates, such as decisions regarding system decomposition, integration strategies, or code structure rules. If applicable, any existing internal standards may be shared on an optional basis.
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.