> That's assuming that things haven't become deeply coupled within the "call stack". Yep; Monolith or SOA you still have to write SOLID code :) > Separating t

> That's assuming that things haven't become deeply coupled within the "call stack". Yep; Monolith or SOA you still have to write SOLID code :) > Separating things across a socket often forces a separation of concerns, which does tend to make refactoring easier. It /should/, and if it does now your changing more than the one variable of "invoked across stacks -> invoked across socket", and are more likely to introduce a regression :)