[ncouture]

What you say is true; I learned, and am still reminded of it, the hard way from time to time.

But it's nothing more than a problem waiting to be solved.

In my case I'm solving this problem by using static sites and managed web hosting.

Put simplicity where simplicity is due and segregate the more complex requirements. Static sites are going a very long way now, and a lot can be done with JavaScript on the client-side with modern browsers.

In many cases no back-end services are needed, but when they are, it can make a lot of sense to segregate them in a way they can power multiple sites with the same functionality requirements.

It's really up to the needs you have but in the end I feel it can really be worth it.

Heck, latest web standards let us componentize elements, we might all be better off with a global database that contains all of them in JSON or YAML format which we can load/dump from and that contains some kind of ACL (ala Firebase can do that).

Have a good day.

[JoshMnem]

Static sites are different. That sounds like a much better model for hosting. It doesn't matter if the servers get destroyed if there is little to clean up.