ArchitectureConference50min
How We Waste Time Building APIs — and the Moment DDD Starts to Matter
This talk explores how teams evolve APIs amid real-world chaos and ownership challenges, revealing when Domain‑Driven Design shifts from theory to practical guidance. It shows how strategic DDD concepts—bounded contexts, ownership, and autonomy—help teams make better design decisions and achieve evolutionary, scalable API development without rigidly “doing full DDD.”
talk.summaryAiDisclaimer
Jacek MilewskiBottega IT Minds | Circle K
talkDetail.whenAndWhere
Thursday, June 18, 15:55-16:45
Room 3
talks.roomOccupancytalks.noOccupancyInfo
Is Domain-Driven Design just a theoretical concept?
When working in the trenches, most teams don’t start with Bounded Contexts or Context Maps. They start with tickets, acceptance criteria, and... the need to ship APIs!
Over time, APIs grow. New consumers appear. Shared resources emerge. And suddenly teams struggle with questions like:
- Who owns this API?
- Can we change this contract?
- Why does every small decision require an architect?
In this talk, I’ll tell the story of how teams naturally evolve APIs in chaos — and why this is not a failure.
I’ll show the moment when Domain-Driven Design stops being theoretical and becomes a practical decision-making tool: helping teams reason about relationships between bounded contexts, ownership, and autonomy — without “doing full DDD”.
This is not a tutorial.
It’s a provocative look at how strategic DDD can support evolutionary API design and team autonomy in large systems.
When working in the trenches, most teams don’t start with Bounded Contexts or Context Maps. They start with tickets, acceptance criteria, and... the need to ship APIs!
Over time, APIs grow. New consumers appear. Shared resources emerge. And suddenly teams struggle with questions like:
- Who owns this API?
- Can we change this contract?
- Why does every small decision require an architect?
In this talk, I’ll tell the story of how teams naturally evolve APIs in chaos — and why this is not a failure.
I’ll show the moment when Domain-Driven Design stops being theoretical and becomes a practical decision-making tool: helping teams reason about relationships between bounded contexts, ownership, and autonomy — without “doing full DDD”.
This is not a tutorial.
It’s a provocative look at how strategic DDD can support evolutionary API design and team autonomy in large systems.
Jacek Milewski
I'm an architect and seasoned software engineer with over 15 years of experience building and evolving large-scale, product-oriented systems.
I work close to the trenches, helping teams design APIs and navigate architectural decisions around ownership, boundaries, and team autonomy - keeping myself as a hands-on expert.
I'm a mentor and trainer at Bottega IT Minds, where I teache Domain-Driven Design pragmatically applied in Microservice architecture supported by AI.
I'm experienced conference speaker, consistently well-rated by attendees, known for practical talks that attract full rooms and spark in-depth discussions.
I work close to the trenches, helping teams design APIs and navigate architectural decisions around ownership, boundaries, and team autonomy - keeping myself as a hands-on expert.
I'm a mentor and trainer at Bottega IT Minds, where I teache Domain-Driven Design pragmatically applied in Microservice architecture supported by AI.
I'm experienced conference speaker, consistently well-rated by attendees, known for practical talks that attract full rooms and spark in-depth discussions.