Re:Goodbye Microservices: From 100s of problem children to 1...
by paxys on Tuesday July 10, 2018 @02:29PM
(#17500880)
Look at the package dependency tree of an average linux program. They are absolutely examples of "microservices" talking to each other.
[ Parent
| on HN ]
Re:Goodbye Microservices: From 100s of problem children to 1...
by digi_owl on Tuesday July 10, 2018 @03:09PM
(#17501176)
And they can be a right mess to wrangle because upstream gets into some artistic frenzy, and shouts down anyone that worries about the ensuing breakages as luddites and haters.
Re:Goodbye Microservices: From 100s of problem children to 1...
by wsy on Tuesday July 10, 2018 @04:55PM
(#17502068)
And still nobody would argue to pack everything together into one executable because of these issues. As everything in software engineering, it is about finding the right trade-off.
Re:Goodbye Microservices: From 100s of problem children to 1...
by digi_owl on Tuesday July 10, 2018 @05:17PM
(#17502266)
Oh, but why do that when we have containers...
Re:Goodbye Microservices: From 100s of problem children to 1...
by lmm on Wednesday July 11, 2018 @06:53AM
(#17505910)
The big problems with microservices come from distributed transactions being difficult and clocks getting out of sync. Multiple services on a single machine don't have that problem.