3 ms·
AWS amplify provide this with automatic previews on github. https://aws.amazon.com/amplify/hosting/ https://aws.amazon.com/amplify/hosting/ Any reason to use
by searchableguy 5y ago
AWS amplify provide this with automatic previews on github.
https://aws.amazon.com/amplify/hosting/ https://aws.amazon.com/amplify/hosting/
Any reason to use Ness over it?
- DoctorOW 5y agoJust looking around at both, there's two main differences. First is the Next.js support right off the bat, Amplify has Lambda support but doesn't optimize automatically. Next is that this is much cheaper. Building isn't done on AWS so using something like Github actions saves you the $0.01 per build minute. Amplify offers 15gb free bandwidth with $0.15/gb in paid version. CloudFront offers 50gb free bandwidth and no more than $0.12/gb. In certain cases Amplify is a better fit but Ness has its place.
- unknown_error 5y agoThank you very much for this answer! That was my #1 question (why this instead of Amplify) after reading the headline and you provided an informative, succinct answer.