Infrastructure as code like using AWS CloudFormation templates to setup a CDN in front of the Puzzle Massive resources. This should not be a requirement to run the Puzzle Massive site, however. I'd imagine that a AWS CloudFront distribution could be placed in front of the site and allow certain routes to either be cached or pass-through to the application. A S3 bucket could, in theory, also be used for storing the puzzle resources and no URLs would need to be changed.
Other services in AWS could be used to lessen the load on a single server. Other Cloud Providers can also be used which is a good case to use something like Terraform to create the resources.
The caveat to all this would be that the site should not require any specific cloud hosting. It should still be able to be deployed on a single server that can be manually set up by running shell scripts.
Infrastructure as code like using AWS CloudFormation templates to setup a CDN in front of the Puzzle Massive resources. This should not be a requirement to run the Puzzle Massive site, however. I'd imagine that a AWS CloudFront distribution could be placed in front of the site and allow certain routes to either be cached or pass-through to the application. A S3 bucket could, in theory, also be used for storing the puzzle resources and no URLs would need to be changed.
Other services in AWS could be used to lessen the load on a single server. Other Cloud Providers can also be used which is a good case to use something like Terraform to create the resources.
The caveat to all this would be that the site should not require any specific cloud hosting. It should still be able to be deployed on a single server that can be manually set up by running shell scripts.
Links to guides and such.