About this Session
As products grow, change becomes harder. New ideas take longer to ship, technical decisions feel risky, and systems start pushing back when teams try to evolve them.
This session looks at how Domain-Driven Design and Hexagonal Architecture help teams design software that can change over time. Through a concrete example, we’ll explore how clear boundaries and a well-defined core make it easier to evolve both the system and the product, whether that means adding new features, integrating AI, changing cloud providers, or adapting infrastructure choices.
Key learnings:
- How clear domain boundaries make systems easier to understand, change, and explain to others
- Practical ways to structure software through a real example, so products can evolve without rewrites
- How architectural boundaries help teams introduce new technologies with less risk
- Techniques for reducing long-term lock-in to frameworks, cloud providers, or platforms
- Common design choices that seem fine early on but make change harder later
By the end of the session, attendees will leave with practical ideas they can apply immediately to design software that can evolve alongside their product, teams, and technology.
