No always on server. Only serverless. If you are starting a new project, I think having a server is better than serverless. With serverless, you'll have to stitch together more 3rd party services to do basic things such as websocket, queue, DB connection pool, etc.
For endpoints that cannot be cached, do customers still have to wait for serverless containers to cold start?
I can’t tell from reading through the docs.
There’s a reference to delegating requests to regular AWS services, so I assume not, but it’s hard to tell without actually setting up free tier, then testing from random geographic locations.
It's specifically CloudFront Functions and not something like Lambda nor Lambda@Edge, so cold start shouldn't be a notable issue but you're far more limited in what you can do with them.
I think this is more suited for simpler use cases if you truly want to stay within the boundaries of the free plan.
I'm not even sure what are the target demographic for this looks like. For builders there are much cheaper options out there with better quotas. Currently the Pro plan gives you 50 GB for $15 and I'm unsure if this is a great deal at all.
