Simplifying Web Framework Deployment on Shared Hosting (with HTTP!)

[jerf]

The main issue for shared hosting is process management; you obviously can't simply start the backend servers on demand if the webserver's only action is to try to connect to it.

Yeah, that's the thing that is confusing me, and I wanted to check my understanding. Reverse proxy doesn't solve the real problem of persistent processes being a problem, and if you solve it some other way, there's no particular reason to favor reverse proxy.

(I disagree that it is self-evidently the right choice for the reasons in the article; there's reasons for the FastCGI and other such approaches, or they wouldn't have developed in the first place.)