Trainings
Over 100 developers and architects trained each year
to help them transform their organizations.
Keywords:
Microservices
Domain Driven Design
Event Storming
AI
AI-Assisted Microservice Architecture with Domain Driven Design and Event Storming
Duration:
4
Days
Target audience:
IT Architects, Tech Leads, Senior Developers, Analysts
AI-Assisted Microservice Architecture with Domain Driven Design and Event Storming
Duration:
4
Days
Target audience:
IT Architects, Tech Leads, Senior Developers, Analysts
AI-Assisted Microservice Architecture with Domain Driven Design and Event Storming
Duration:
4
Days
Target audience:
IT Architects, Tech Leads, Senior Developers, Analysts
Goal and Benefits
The goal of this training is to learn how to design microservice architectures using Domain-Driven Design and Event Storming, while using AI in a mature and responsible way.
AI in this training shortens the time required to make architectural decisions and reduces the cost of wrong choices – from the very first Event Storming session to working with legacy systems – without transferring responsibility for architecture to AI.
Business insight, AI, Event Storming, and DDD are used here as tools for analysis, design, structuring, decision-making, and controlling system evolution, not as academic, greenfield-only techniques.
Goal and Benefits
The goal of this training is to learn how to design microservice architectures using Domain-Driven Design and Event Storming, while using AI in a mature and responsible way.
AI in this training shortens the time required to make architectural decisions and reduces the cost of wrong choices – from the very first Event Storming session to working with legacy systems – without transferring responsibility for architecture to AI.
Business insight, AI, Event Storming, and DDD are used here as tools for analysis, design, structuring, decision-making, and controlling system evolution, not as academic, greenfield-only techniques.
Goal and Benefits
The goal of this training is to learn how to design microservice architectures using Domain-Driven Design and Event Storming, while using AI in a mature and responsible way.
AI in this training shortens the time required to make architectural decisions and reduces the cost of wrong choices – from the very first Event Storming session to working with legacy systems – without transferring responsibility for architecture to AI.
Business insight, AI, Event Storming, and DDD are used here as tools for analysis, design, structuring, decision-making, and controlling system evolution, not as academic, greenfield-only techniques.
My Digital Twin: It'll stay with You for Longer
Participants receive exclusive access to the Trainer’s Digital Twin – a personalized model embedded in the Trainer’s experience and way of thinking. The Trainer stays with you for longer, long after the workshops are finished, and the Digital Twin will be continuously improved.
The Digital Twin has been trained on dozens of hours of transcripts, private materials, notes, interpretations, and experience – including those that go beyond the scope of the training itself. Participants gain access to a sparring partner, support in everyday architectural decisions, analysis, and consultation – reflecting what the Trainer’s perspective might be on a given aspect of their system.
My Digital Twin: It'll stay with You for Longer
Participants receive exclusive access to the Trainer’s Digital Twin – a personalized model embedded in the Trainer’s experience and way of thinking. The Trainer stays with you for longer, long after the workshops are finished, and the Digital Twin will be continuously improved.
The Digital Twin has been trained on dozens of hours of transcripts, private materials, notes, interpretations, and experience – including those that go beyond the scope of the training itself. Participants gain access to a sparring partner, support in everyday architectural decisions, analysis, and consultation – reflecting what the Trainer’s perspective might be on a given aspect of their system.
My Digital Twin: It'll stay with You for Longer
Participants receive exclusive access to the Trainer’s Digital Twin – a personalized model embedded in the Trainer’s experience and way of thinking. The Trainer stays with you for longer, long after the workshops are finished, and the Digital Twin will be continuously improved.
The Digital Twin has been trained on dozens of hours of transcripts, private materials, notes, interpretations, and experience – including those that go beyond the scope of the training itself. Participants gain access to a sparring partner, support in everyday architectural decisions, analysis, and consultation – reflecting what the Trainer’s perspective might be on a given aspect of their system.
AI in this training
Participates in every stage of design – from domain exploration, through architectural decisions, to legacy evolution – always as a thinking partner, not an automatic decision-maker
Acts as a partner in architectural work within DDD and Microservices – both for critical tasks and the unwanted, time-consuming ones
AI in this training
Participates in every stage of design – from domain exploration, through architectural decisions, to legacy evolution – always as a thinking partner, not an automatic decision-maker
Acts as a partner in architectural work within DDD and Microservices – both for critical tasks and the unwanted, time-consuming ones
AI in this training
Participates in every stage of design – from domain exploration, through architectural decisions, to legacy evolution – always as a thinking partner, not an automatic decision-maker
Acts as a partner in architectural work within DDD and Microservices – both for critical tasks and the unwanted, time-consuming ones
Training differentiators
AI used in a mature way: It supports decisions, analysis, design, and documentation – exactly where architects lose the most time today.
Trainer’s Digital Twin that stays with you: Participants receive access to the Trainer’s Digital Twin – a preserved way of thinking, heuristics, and experience that can be used long after the training ends.
Brownfield‑friendly: The training shows, using a simple example, how to work with systems that already exist, even though the example itself may appear greenfield.
Training differentiators
AI used in a mature way: It supports decisions, analysis, design, and documentation – exactly where architects lose the most time today.
Trainer’s Digital Twin that stays with you: Participants receive access to the Trainer’s Digital Twin – a preserved way of thinking, heuristics, and experience that can be used long after the training ends.
Brownfield‑friendly: The training shows, using a simple example, how to work with systems that already exist, even though the example itself may appear greenfield.
Training differentiators
AI used in a mature way: It supports decisions, analysis, design, and documentation – exactly where architects lose the most time today.
Trainer’s Digital Twin that stays with you: Participants receive access to the Trainer’s Digital Twin – a preserved way of thinking, heuristics, and experience that can be used long after the training ends.
Brownfield‑friendly: The training shows, using a simple example, how to work with systems that already exist, even though the example itself may appear greenfield.
Participants
Participants are architects, technical leaders, and developers facing the complexity of delivering business products and designing microservice architectures, who want to broaden their knowledge with strategies that support a pragmatic approach to these challenges. The training systematizes complex topics into flexible methods that provide safety and scalability.
Participants will:
Gain control over architectural complexity: Learn how to organize domains, processes, and system boundaries even when the architecture is already “living its own life.”
Understand the causes and effects of the current state of their project: trade-offs, postponed decisions, and apparent constraints.
Make better architectural decisions with lower cognitive cost: AI as a partner helps reveal consequences, risks, and alternatives faster.
Participants
Participants are architects, technical leaders, and developers facing the complexity of delivering business products and designing microservice architectures, who want to broaden their knowledge with strategies that support a pragmatic approach to these challenges. The training systematizes complex topics into flexible methods that provide safety and scalability.
Participants will:
Gain control over architectural complexity: Learn how to organize domains, processes, and system boundaries even when the architecture is already “living its own life.”
Understand the causes and effects of the current state of their project: trade-offs, postponed decisions, and apparent constraints.
Make better architectural decisions with lower cognitive cost: AI as a partner helps reveal consequences, risks, and alternatives faster.
Participants
Participants are architects, technical leaders, and developers facing the complexity of delivering business products and designing microservice architectures, who want to broaden their knowledge with strategies that support a pragmatic approach to these challenges. The training systematizes complex topics into flexible methods that provide safety and scalability.
Participants will:
Gain control over architectural complexity: Learn how to organize domains, processes, and system boundaries even when the architecture is already “living its own life.”
Understand the causes and effects of the current state of their project: trade-offs, postponed decisions, and apparent constraints.
Make better architectural decisions with lower cognitive cost: AI as a partner helps reveal consequences, risks, and alternatives faster.
Training Program
1. Foundations of microservice architecture, DDD, and Event Storming
Why microservices – autonomy, team scaling, but also cost
DDD as a practical architect’s tool, stripped of theoretical overhead and academic debates
Event Storming as a technique for discovering architecture, together with learning business insight
Capabilities and limitations of AI: knowledge, heuristics, gaps
2. A key shift in modern architecture
Today business teaches IT how to build an MVP – who the Product Engineer is
Refinements cut in half
The architect and the illusion of control – how autonomous teams allow you to remain safely within it
You are a leader, people are also your responsibility – how to help each other
3. Big Picture Event Storming – understanding the domain with AI
Chaotic phase and chronology – how not to lose the meaning of the process
AI as support for domain exploration
Experience-based simulations
Filtering events that pretend to be domain events, and when they still matter
Direct transformation of workshop sticky notes into classes, lines of code, and architectural decisions
4. Process Level Event Storming and its real significance for architecture
From process to system responsibilities
The most effective facilitation techniques with AI
Every sticky note fulfills the goal of a business-aware architect
5. Discovering subdomains and defining Bounded Contexts
Heuristics for discovering subdomains
AI Domain Mapper – grouping events into archetypal areas
Candidates for bounded contexts and their real meaning
Typical anti-patterns
6. Context mapping and large-scale structure
What true microservice architecture really is
The essence of a context map, not an artifact created just to “exist”
Communication is not an API: how strategically important your everyday decisions are
What Capability and Platform really mean – what everyone is striving for
7. Communication between bounded contexts
Shortening and simplifying communication-related decisions
Understanding consequences instead of discovering them later and fixing them at high cost
How to choose one of 3 communication styles and one of 14 message delivery approaches
Synchronous / asynchronous, orchestration / choreography – additional layers of communication complexity
The cost of failure when testing communication in test environments and end-to-end tests
8. Simulations, risks, and process resilience
AI Virtual Roles: what about missing perspectives?
Techniques for dealing with a narrowed viewpoint of Event Storming workshop participants
Identifying risks, compensations, and architectural consequences
9. Architectural decisions with AI
What makes a decision “hard”
Whether to split bounded contexts or not
Modular monolith vs microservices – hidden trade-offs
How not to have to write yet another ADR
10. Tactical DDD – from process to aggregates
Discovering aggregate boundaries in Process and Design Level Event Storming
A different look at the same heuristics
AI Tactical DDD Helper
Code as a consequence of the model, not the starting point
11. Legacy and brownfield – evolutionary architecture
Why learning greenfield modeling is crucial when working with legacy systems
Big bang rewrite, Strangler Pattern, Bubble Context, Anti‑Corruption Layer, Autonomous Context
AI Legacy Explorer: analysis of dirty code and processes, identification of cut lines
Combining Event Storming techniques with existing architecture
12. Documentation that says what it should
Today: anticipating potential questions of future documentation readers
The future: AI and asking any question about all knowledge distributed across the organization
Overview of approaches to building your own agents (crewAI, semantic layers, SLMs)
Training Program
1. Foundations of microservice architecture, DDD, and Event Storming
Why microservices – autonomy, team scaling, but also cost
DDD as a practical architect’s tool, stripped of theoretical overhead and academic debates
Event Storming as a technique for discovering architecture, together with learning business insight
Capabilities and limitations of AI: knowledge, heuristics, gaps
2. A key shift in modern architecture
Today business teaches IT how to build an MVP – who the Product Engineer is
Refinements cut in half
The architect and the illusion of control – how autonomous teams allow you to remain safely within it
You are a leader, people are also your responsibility – how to help each other
3. Big Picture Event Storming – understanding the domain with AI
Chaotic phase and chronology – how not to lose the meaning of the process
AI as support for domain exploration
Experience-based simulations
Filtering events that pretend to be domain events, and when they still matter
Direct transformation of workshop sticky notes into classes, lines of code, and architectural decisions
4. Process Level Event Storming and its real significance for architecture
From process to system responsibilities
The most effective facilitation techniques with AI
Every sticky note fulfills the goal of a business-aware architect
5. Discovering subdomains and defining Bounded Contexts
Heuristics for discovering subdomains
AI Domain Mapper – grouping events into archetypal areas
Candidates for bounded contexts and their real meaning
Typical anti-patterns
6. Context mapping and large-scale structure
What true microservice architecture really is
The essence of a context map, not an artifact created just to “exist”
Communication is not an API: how strategically important your everyday decisions are
What Capability and Platform really mean – what everyone is striving for
7. Communication between bounded contexts
Shortening and simplifying communication-related decisions
Understanding consequences instead of discovering them later and fixing them at high cost
How to choose one of 3 communication styles and one of 14 message delivery approaches
Synchronous / asynchronous, orchestration / choreography – additional layers of communication complexity
The cost of failure when testing communication in test environments and end-to-end tests
8. Simulations, risks, and process resilience
AI Virtual Roles: what about missing perspectives?
Techniques for dealing with a narrowed viewpoint of Event Storming workshop participants
Identifying risks, compensations, and architectural consequences
9. Architectural decisions with AI
What makes a decision “hard”
Whether to split bounded contexts or not
Modular monolith vs microservices – hidden trade-offs
How not to have to write yet another ADR
10. Tactical DDD – from process to aggregates
Discovering aggregate boundaries in Process and Design Level Event Storming
A different look at the same heuristics
AI Tactical DDD Helper
Code as a consequence of the model, not the starting point
11. Legacy and brownfield – evolutionary architecture
Why learning greenfield modeling is crucial when working with legacy systems
Big bang rewrite, Strangler Pattern, Bubble Context, Anti‑Corruption Layer, Autonomous Context
AI Legacy Explorer: analysis of dirty code and processes, identification of cut lines
Combining Event Storming techniques with existing architecture
12. Documentation that says what it should
Today: anticipating potential questions of future documentation readers
The future: AI and asking any question about all knowledge distributed across the organization
Overview of approaches to building your own agents (crewAI, semantic layers, SLMs)
Training Program
1. Foundations of microservice architecture, DDD, and Event Storming
Why microservices – autonomy, team scaling, but also cost
DDD as a practical architect’s tool, stripped of theoretical overhead and academic debates
Event Storming as a technique for discovering architecture, together with learning business insight
Capabilities and limitations of AI: knowledge, heuristics, gaps
2. A key shift in modern architecture
Today business teaches IT how to build an MVP – who the Product Engineer is
Refinements cut in half
The architect and the illusion of control – how autonomous teams allow you to remain safely within it
You are a leader, people are also your responsibility – how to help each other
3. Big Picture Event Storming – understanding the domain with AI
Chaotic phase and chronology – how not to lose the meaning of the process
AI as support for domain exploration
Experience-based simulations
Filtering events that pretend to be domain events, and when they still matter
Direct transformation of workshop sticky notes into classes, lines of code, and architectural decisions
4. Process Level Event Storming and its real significance for architecture
From process to system responsibilities
The most effective facilitation techniques with AI
Every sticky note fulfills the goal of a business-aware architect
5. Discovering subdomains and defining Bounded Contexts
Heuristics for discovering subdomains
AI Domain Mapper – grouping events into archetypal areas
Candidates for bounded contexts and their real meaning
Typical anti-patterns
6. Context mapping and large-scale structure
What true microservice architecture really is
The essence of a context map, not an artifact created just to “exist”
Communication is not an API: how strategically important your everyday decisions are
What Capability and Platform really mean – what everyone is striving for
7. Communication between bounded contexts
Shortening and simplifying communication-related decisions
Understanding consequences instead of discovering them later and fixing them at high cost
How to choose one of 3 communication styles and one of 14 message delivery approaches
Synchronous / asynchronous, orchestration / choreography – additional layers of communication complexity
The cost of failure when testing communication in test environments and end-to-end tests
8. Simulations, risks, and process resilience
AI Virtual Roles: what about missing perspectives?
Techniques for dealing with a narrowed viewpoint of Event Storming workshop participants
Identifying risks, compensations, and architectural consequences
9. Architectural decisions with AI
What makes a decision “hard”
Whether to split bounded contexts or not
Modular monolith vs microservices – hidden trade-offs
How not to have to write yet another ADR
10. Tactical DDD – from process to aggregates
Discovering aggregate boundaries in Process and Design Level Event Storming
A different look at the same heuristics
AI Tactical DDD Helper
Code as a consequence of the model, not the starting point
11. Legacy and brownfield – evolutionary architecture
Why learning greenfield modeling is crucial when working with legacy systems
Big bang rewrite, Strangler Pattern, Bubble Context, Anti‑Corruption Layer, Autonomous Context
AI Legacy Explorer: analysis of dirty code and processes, identification of cut lines
Combining Event Storming techniques with existing architecture
12. Documentation that says what it should
Today: anticipating potential questions of future documentation readers
The future: AI and asking any question about all knowledge distributed across the organization
Overview of approaches to building your own agents (crewAI, semantic layers, SLMs)