I must be an oddball because these services never really made sense to me.<p>I don't want to use their CI. I already have CI for running tests and other validations. I don't want to have a separate single-threaded CI stack with bare minimum features for building the site.<p>These all have "atomic" deploys which cause problems with hash-named assets as you get 404s during the transition.<p>What I basically want is something that I can rsync to and that is served by a CDN. I've ended up with S3+CloudFront but it doesn't have all of the nice features you may want from a static site host like index pages, but that is pretty easy to work around.
I don't known why he didn't investigate previous benchmarks for static site hosting.
Github Pages was always the best option, by far. Fastest and free.
fwiw, the reason github pages is the fastest is because they're cached by fastly. you can cut out the middle man and put your static site directly on their edgecompute platform now (up to 50MB): <a href="https://www.fastly.com/blog/no-origin-static-websites-at-the-edge" rel="nofollow">https://www.fastly.com/blog/no-origin-static-websites-at-the...</a>
In my experience, Amplify as a platform has been a nightmare to work with. It claims fast prototyping and developer convenience but the constant random failed deployments and the flaky CLI drain the momentum you would have with a batteries-included platform. I highly suggest to avoid this platform.
This was interesting to read. I recently changed from Drupal to WordPress and now I'm thinking something more static would be better. Good to know all my options.
a box in your closet or bare metal in the datacenter, repectively?<p>While you read the TOS end-to-end (you do that, right?), I finish the site and have lunch.