World Congress 2026 Europe - Virtual Stage Jul 2, 2026 Session details

How We Waste Time Building APIs — and the Moment DDD Starts to Matter

Jacek Milewski

Are innocent feature requests silently destroying your team's autonomy? Discover how applying Domain-Driven Design at the exact right moment rescues leaking API architectures.

Pause
Mute Enter Fullscreen
#1 about 5 min

Building the initial training planner API

How early system design choices manifest as strategic decisions in API development.

#2 about 2 min

Why cloning services creates architectural duplication

The consequences of forking repositories to support isolated business tickets.

#3 about 5 min

Coupling services to handle cancellation fees

How adding business rules to operational endpoints creates tight coupling and misplaced responsibilities.

#4 about 3 min

Recognizing crossed service boundaries in systems

Understanding the negative impacts of teams making isolated decisions that cross domain boundaries.

#5 about 6 min

Applying domain-driven design principles to APIs

Using bounded contexts and capability layers to evaluate architectural boundaries.

#6 about 6 min

Defining boundaries for planning and booking

Separating the strategic training planner from the operational resource booking context.

#7 about 4 min

Using simulations to test system architecture

Generating hypothetical scenarios to uncover hidden requirements and missing domain concepts.

#8 about 3 min

Prioritizing feature implementations based on cost

Deciding when to support new system capabilities by analyzing likelihood and future complexity.

#9 about 4 min

Making clean architecture decisions iteratively and rapidly

Minimizing delivery overhead by stabilizing small architectural decision records.

#10 about 5 min

Aligning context relations with team topologies

Using the open host service pattern and streamlined teams to clarify API responsibilities.

#11 about 3 min

Modeling event economics and financial logic

Ensuring business logic resides in the service that owns the financial decision, not just the data.

Matching moments

43 sec

Establishing a concrete vision for REST API development

Wekoslav Stefanovski Wekoslav Stefanovski · World Congress 2026 Europe

3:10 min

Understanding the core concepts of API design

Alen Pokos · LIVE

1:40 min

Summarizing key engineering lessons for platform API development

Anto Anto · World Congress 2024

2:20 min

How the inevitable march of time breaks software patterns

Peter Kröner Peter Kröner · World Congress 2023

1:22 min

Structuring engineering teams around domain bounded contexts

Tom George · LIVE

4:33 min

Building long-term Angular architectures with domain-driven design

Manfred Steyer Manfred Steyer · LIVE

Upcoming sessions on this topic

Open session

World Congress 2026 North America

Designing APIs That Survive AI Agents at Scale

Phani Pendurthi

Mastercard, Principal Software Engineer

Phani Pendurthi
Open session

World Congress 2026 North America

API = Some REST and HTTP, right? RIGHT?!

Rustam Mehmandarov

Passionate computer scientist

Rustam Mehmandarov
Open session

World Congress 2026 North America

Reinventing Testing Practices in the AI Era

Eric Deandrea

Java Champion & Senior Principal Software Engineer, IBM

Eric Deandrea
Open session

World Congress 2026 North America

public void saveMoney(AI): The Developer's Guide to Unit Economics

Hrushikesh Pokala

Senior Software Engineer Lead at Equifax

Hrushikesh Pokala
Open session

World Congress 2026 North America

Optimizing consumption and cost of AI APIs in the enterprise

Derric Gilling

Vice President and General Manager, API Platform

Derric Gilling
Open session

World Congress 2026 North America

AI-Driven API Design

Mike Amundsen

Author, Adviser, Trainer

Mike Amundsen