The problem that Netlify has is that they are simply a feature of the big cloud providers.
Microsoft is already testing the waters with their own offering and I'm sure AWS and Google are as well. I'm not sure Netlify will survive the onslaught.
Microsoft is already testing the waters with their own offering and I'm sure AWS and Google are as well. I'm not sure Netlify will survive the onslaught.
there are a LOT of pain points to deal with rolling out all that is included with the base netlify offering
hosting a static site is pretty easy - but configuring routing between cloudfront and s3 can be complicated so that the reequests don't always reference the root index.html
creating an autodeploy infrastructure can be challenging as well, tools like github actions might make that a little easier, but there are a lot of considerations there
it also makes these kinds of solutions more accessible to developers who might not have the understanding or interest to set up that kind of infrastructure. front end devs can build sites, connect, and go with little fuss
I think the market is larger for simplified services without the IAM and S3 cruft, especially when you have to educate the client on the solution.
Their redirects are a pain point though.