> By their nature, microservices require you to define what each service is responsible for. Akin to waterfall development, this means making structural choices

> By their nature, microservices require you to define what each service is responsible for. Akin to waterfall development, this means making structural choices before you’ve had a chance to observe the system. These definitions inevitably end up being incorrect, as you know the least about your domain in the beginning. This is a terrible analog. Interfaces, versioning, and composite services address all of this.