Microservices Can Wait

> 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.

Re: Microservices Can Wait

#5

Post by Miniminix » Tue, Nov 05, 2024, 7:47 PM UTC

brodouevencode wrote: post #4

> 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.

Not disagreeing with you, but do you have a link on process which includes your callouts would work for micro services?

Re: Microservices Can Wait

#6

Post by Miniminix » Tue, Nov 05, 2024, 7:55 PM UTC

For an article like this, what is the difference between a service and a microservice?

Seems to lots of space between monolith and microservice