News for hackers. Stuff that matters.
Re:Microservices Can Wait by brodouevencode on Tuesday November 05, 2024 @11:27AM (#42052832)
> 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 by Miniminix on Tuesday November 05, 2024 @02:47PM (#42054603)
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 by asvirts on Tuesday November 05, 2024 @11:20AM (#42052761)
"Don’t solve for problems you don’t yet have"
Re:Microservices Can Wait by Miniminix on Tuesday November 05, 2024 @02:55PM (#42054660)
For an article like this, what is the difference between a service and a microservice?

Seems to lots of space between monolith and microservice