3 ms·

If I'm reading the source html pages of "servethehome.com" correctly, it's a Wordpress site and that's what Patrick is basing hosting cost comparisons on. I've

by jasode 6y ago

If I'm reading the source html pages of "servethehome.com" correctly, it's a Wordpress site and that's what Patrick is basing hosting cost comparisons on. I've mentioned before[0] that AWS too expensive and overkill for Wordpress sites (especially simpler non-ecommerce ones). I don't think this conclusion is controversial. Simpler hosting requirements is why Patrick only has to spend 4 hours of labor in 1 year to upgrade some hardware. It's when you need the higher-level value-added services of AWS services (Dynamo, Redshift, region failover, etc) that the comparison becomes more complicated. E.g. Companies with mission-critical transactional websites or mobile backends are more complex and they need agility to add/change the infrastructure landscape in response to unknown workloads. They don't have the money (or expertise) to code an in-house version of AWS services portfolio. E.g.[1] [0] https://news.ycombinator.com/item?id=10797166 https://news.ycombinator.com/item?id=10797166 [1] https://www.cbronline.com/news/guardian-aws-migration https://www.cbronline.com/news/guardian-aws-migration older archive: https://web.archive.org/web/20160319022029/https://www.computerworlduk.com/cloud-computing/guardian-goes-all-in-on-aws-public-cloud-after-openstack-disaster-3629790/ https://web.archive.org/web/20160319022029/https://www.compu...

Patrick-STH 6y ago
Totally correct. I mention that a bit in the video as well. Also - I do not view this as an AWS v. Colo. We use AWS for some services as well so it is a specific part of the workload we run (not just WP) that is in our hosting cluster. And again, this is a fraction of what we have in data cetners due to the labs and such.
rsanheim 6y ago
Exactly this. A lot of the conversation here is missing a key point of these hosting debates: context is _everything_.
sofixa 6y ago
Wordpress hosting is expensive and overkill to do on AWS if you do it traditionalally. Add simply static or a similar plugin, whip up a script to upload the static HTML to S3, set up Cloudfront with good cache, and you're done. Your site is faster, more secure, cheaper and can easily run on a t3.micro for peanuts. Only gotcha is comments, but it's a solved problem ( disqus or any of the alternatives) and similar.

by jasode 6y ago

Patrick-STH 6y ago

Totally correct. I mention that a bit in the video as well. Also - I do not view this as an AWS v. Colo. We use AWS for some services as well so it is a specific part of the workload we run (not just WP) that is in our hosting cluster. And again, this is a fraction of what we have in data cetners due to the labs and such.

rsanheim 6y ago

Exactly this. A lot of the conversation here is missing a key point of these hosting debates: context is _everything_.

sofixa 6y ago

Wordpress hosting is expensive and overkill to do on AWS if you do it traditionalally. Add simply static or a similar plugin, whip up a script to upload the static HTML to S3, set up Cloudfront with good cache, and you're done. Your site is faster, more secure, cheaper and can easily run on a t3.micro for peanuts. Only gotcha is comments, but it's a solved problem ( disqus or any of the alternatives) and similar.