4 ms·
>simplifying stuff anywhere is possible https://raw.githubusercontent.com/aws-samples/aws-refarch-wordpress/master/images/aws-refarch-wordpress-v20171026.jpeg
by numlock86 6y ago
>simplifying stuff anywhere is possible
https://raw.githubusercontent.com/aws-samples/aws-refarch-wordpress/master/images/aws-refarch-wordpress-v20171026.jpeg https://raw.githubusercontent.com/aws-samples/aws-refarch-wo...
Ironically, that's how you are supposed to run Wordpress on AWS.
- alharith 6y agoUnironically, this is one of the simpler setups for a multi-node WP setup I have seen, and I have set up prod WP many times. Anyone with associate level knowledge of AWS can do this. There is a reason there are entire companies (pantheon) dedicated to hosting Wordpress for you: doing it with speed, resiliency and redundancy is hard.
- owenmarshall 6y agoMeta: I've vouched for this comment. You appear to be shadowbanned.
- alharith 6y agoThey don't like conservative opinions here, so I am not surprised.
- ex_amazon_sde 6y agoYou seem to be confusing Amazon's internal infrastructure and its development model to how AWS is used by customers.
- numlock86 6y agoI would have posted internal slides directly from app architects or even service(-prototyping) dev teams within AWS including similar vibes regarding this discussion, but for obvious reasons that's not a good idea. But whom am I telling that ... That "reference architecture" aimed at customers using their infrastructure regarding a Wordpress installation gets the general idea across, though.
- regularfry 6y agoThat's the result though, right? Radical internal simplicity forces incidental external complexity.
- ex_amazon_sde 6y agoNo, I'm talking about internal services that aren't directly exposed through AWS API. This represent the large majority of the internal codebase.
- ComodoHacker 6y agoWould it be any simpler when running on-prem or in another cloud?