The success of a microservice implementation ultimately comes down to its ability to adapt to change, change that comes at varying speeds in different parts of the overall system. In order to have a resilient system, design thinking is needed at all levels, and especially when designing the APIs that are the coupling mechanism for components in the system. The sessions in this track will explore the methods leading organizations are using to define context maps for their microservice systems, effective boundaries between different domains in the system, and the details of the APIs used for communication between microservices in the system.