[arinlen]

> As in, "we have a PHP monolith used by all of 12 people in the accounting department, and for some reason we've been tasked with making it run on multiple machines ("for redundancy" or something) by next month.

I find this comment highly ignorant. The need to deploy a distributed system is not always tied to performance or scalability or reliability.

Sometimes all it takes is having to reuse a system developed by a third party, or consume an API.

Do you believe you'll always have the luxury of having a single process working on a single machine that does zero communication over a network?

Hell, even a SPA calling your backend is a distributed system. Is this not a terribly common usecase?

Enough about these ignorant comments. They add nothing to the discussion and are completely detach from reality

[phtrivier]

I failed to make the requester sound more obnoxious than the request.

My point is precisely that transitioning from a single app on a machine is a natural and necessary part of a system's life, but that I can't find satisfying resources on how to handle thise phase, as opposed to handling much higher load.

Sorry for the missed joke.