>it's easier for some devs to cleanly separate concerns when they're forced to do so by the constraint of process separation This is a dangerous ideology. Proc

>it's easier for some devs to cleanly separate concerns when they're forced to do so by the constraint of process separation This is a dangerous ideology. Process separation doesn't enforce loose coupling, it simply makes the pain of tight coupling between them that much worse. I worked on a "microservice" system once where I regularly had to debug a problem across four different service boundaries and two different languages. It felt like I was using boxing gloves to perform surgery on a rube goldberg toy.