AI coding agents can generate working applications remarkably quickly. Unfortunately, working code isn't necessarily well-designed, readable, or maintainable code. Agents can scatter business logic across application layers, ignore architectural boundaries, and produce code that is difficult to maintain and evolve.
Domain-Driven Design is not a new idea. Eric Evans published Domain-Driven Design: Tackling Complexity in the Heart of Software in 2003. DDD adoption grew with the rise of microservices, and today, as agents make implementation dramatically faster, domain modeling and enforcing architectural boundaries are even more important.

Domain-Driven Design provides a repeatable structure for implementing complex business logic. Hexagonal Architecture separates the business domain from infrastructure and framework boilerplate. Together they enable developers to focus on modeling the business while delegating much of the implementation to coding agents.
In this session, we'll build an application using Domain-Driven Design, Hexagonal Architecture, and AI coding agents. We'll explore:
• Modeling the domain: Using Ubiquitous Language, Aggregates, Value Objects, Services, and Repositories to express business rules and behavior
• Separating concerns: Using Hexagonal Architecture to isolate business logic from databases, APIs, messaging, and other infrastructure
• Coaching agents: Creating Skills that teach coding agents how to consistently implement DDD patterns
• Testing DDD: Using automated tests to both enforce architectural boundaries and verify business rules
You'll leave with practical techniques for combining DDD and agentic coding to build applications that are not only functional, but well-structured, testable, and maintainable.
No slides. Just live code, coding agents, and Domain-Driven Design.