A PRACTICAL COURSE FOR SOFTWARE DEVELOPERS & TECHNICAL LEADS
Design applications that hold up in production.
Understand the infrastructure, the code, and the decisions that connect them.
Upcoming sessions and pricing on request.
Requirements change. Dependencies grow. Networks fail. The course explores how architecture choices play out in these situations, through practical exercises and discussions about the trade-offs.
Understand the constraints. Connect technical decisions to what the system needs to deliver.
Work through the consequences. Use code and group challenges to examine the design.
WHAT WE’LL EXPLORE
Four technical parts, followed by how to put them into practice with teams.
NFRs & INFRASTRUCTURE
Start with the non-functional requirements. Understand what reliability means for your application, then make infrastructure choices that support it.
How much downtime and data loss can the business tolerate, and what does that mean for your infrastructure?
CLASSES & DEPENDENCIES
Manage complexity inside the codebase. Structure responsibilities and dependencies so that changes stay understandable as the application grows.
When a requirement changes, how much of your application needs to change with it?
DOMAIN-DRIVEN DESIGN
Explore the domain with the people who understand it. Use that knowledge to find meaningful boundaries and build models that express the business rules.
Where should a business rule live, and which changes need to stay consistent together?
DISTRIBUTED SYSTEMS
Understand when distribution helps and what it costs. Design communication and failure handling so that independently running parts can work together reliably.
What happens when a call times out, a message arrives twice, or only half of a workflow succeeds?
THE ARCHITECT IN PRACTICE
Bring the technical decisions into everyday delivery. Clarify requirements with stakeholders, communicate trade-offs, and stay involved through implementation.
How do you communicate your architecture, document the decisions behind it, and guide the team through implementation?
You should be comfortable working in an existing codebase. The practical examples use .NET and Azure; familiarity with C# will help.
YOUR INSTRUCTOR
Software Engineer
Software Architecture Trainer
I’m a software engineer and trainer with over 15 years of experience working on warehouse automation, logistics, and intelligent document processing systems.
My interests include building infrastructure with cloud-native technologies, distributed systems, and domain-driven design. I enjoy working through architectural questions and staying close to the implementation to understand how those decisions work in practice.
I also teach software architecture, using practical exercises and examples from project experience to explore design choices and their trade-offs.
Software for automated warehouses, bringing together domain modelling, event-driven workflows, and cloud infrastructure to support everyday operations.
Helping machine learning and generative AI models run across regions, with attention to reliability, response times, and how the services work together.
Working with teams on logistics and insurance applications, using Clean Architecture and shaping the design through conversations, coding, and reviews.
“What I liked most was the broad view of software architecture. We covered a range of topics, instead of staying on just one thing, and the number of exercises felt about right.”
“The mix of solo and group exercises worked really well. The slides were visual, not just a bunch of bullet points, and that helped a lot. Andrei was an excellent tutor.”
“The examples made the concepts easy to follow. I don’t have much experience with C# or .NET, but the trainer adjusted the explanations and drew comparisons with Java. That really helped me keep up.”
“I came away with new ways of looking at things and plenty to digest. I liked breaking into small groups for the exercises. It gave us a chance to work things out for ourselves between presentations :)”
Tell me a little about your experience and what you’d like to learn. We can discuss the course, upcoming sessions, format, and pricing.