We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
From Domain Boundaries to Software Architecture - Maxime Sanglan-Charlier
Learn how to determine domain boundaries and translate them into software architecture, exploring key takeaways including event storming, domain-driven design, and stakeholder involvement.
- Domain-driven design is essential for determining software architecture
- Identify domain boundaries by creating a canvas with different areas, such as business rules, data, and messages
- Use event storming to identify patterns and relationships between events
- Consider the cohesion and coupling between components when determining domain boundaries
- Domain boundaries are not fixed and can change over time
- Use techniques such as Event Storming Cheat Sheet to identify potential domain boundaries
- Involve domain experts and stakeholders in the process of identifying domain boundaries
- Domain boundaries can be difficult to determine, but using techniques such as event storming and message flow modeling can help
- Maintain a clear picture of the domain boundaries through visualization
- Domain boundaries can impact the overall architecture of the software.