3 ms·
Microservices Can Wait
- asvirts 2y ago"Don’t solve for problems you don’t yet have"
- deleted 2y ago[deleted]
- brodouevencode 2y ago> 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.
- Miniminix 2y agoNot disagreeing with you, but do you have a link on process which includes your callouts would work for micro services?
- Miniminix 2y agoFor an article like this, what is the difference between a service and a microservice? Seems to lots of space between monolith and microservice