3 ms·

It seems like for that kind of site what you're really looking for is completely static content behind a CDN. Your average blog or corporate homepage doesn't ne

It seems like for that kind of site what you're really looking for is completely static content behind a CDN. Your average blog or corporate homepage doesn't need to be dynamic at page-load time. You can generate the pages with a template engine when you update them, and then serve up the static content. If you want to power some little dynamic things like blog comments you can run a custom microservice in a less awful programming language, or go with some hosted cloud option like AWS AppSync or Aurora Serverless.

mgkimsal 8y ago
So one should increase their reliance on third party services, potentially having their small site requiring two or three external services (potentially at different providers) instead of just having it all in one package (in PHP or anything else)?
- brianpgordon 8y ago
  So one should dynamically generate the page's markup for every single page view? With the attack surface that comes with exposing your PHP site to the public internet? Are you going to conscientiously check for security updates on your server? Are you going to trust whatever CMS you're using to win the whack-a-mole game of patching vulns (and god help you if it's Wordpress)? Are you going to stand up and maintain your own database server? Can you scale up capacity if you need it? Have you thought about backups? The "all in one package" solution is a lot more complex than you make it sound. I would argue that much of the 80% of the web powered by PHP would be well-advised to utilize cloud services.
  - mgkimsal 8y ago
    > So one should dynamically generate the page's markup for every single page view yes.
    - brianpgordon 8y ago
      The point of me copying the structure of your comment with my own is to point out that your line of argument ("look at how complex this seems on its face") applies just as well to your own position as it does mine. When you say "yes" you're just repeating the same argument that I used to refute yours. I don't get it.

mgkimsal 8y ago

So one should increase their reliance on third party services, potentially having their small site requiring two or three external services (potentially at different providers) instead of just having it all in one package (in PHP or anything else)?

brianpgordon 8y ago
So one should dynamically generate the page's markup for every single page view? With the attack surface that comes with exposing your PHP site to the public internet? Are you going to conscientiously check for security updates on your server? Are you going to trust whatever CMS you're using to win the whack-a-mole game of patching vulns (and god help you if it's Wordpress)? Are you going to stand up and maintain your own database server? Can you scale up capacity if you need it? Have you thought about backups? The "all in one package" solution is a lot more complex than you make it sound. I would argue that much of the 80% of the web powered by PHP would be well-advised to utilize cloud services.
- mgkimsal 8y ago
  > So one should dynamically generate the page's markup for every single page view yes.
  - brianpgordon 8y ago
    The point of me copying the structure of your comment with my own is to point out that your line of argument ("look at how complex this seems on its face") applies just as well to your own position as it does mine. When you say "yes" you're just repeating the same argument that I used to refute yours. I don't get it.