[pier25]

> Serverless container services such as Heroku, Netlify, AWS ECS/EKS Fargate, Google Kubernetes Engine, and Azure Kubernetes Service

IMO I don't think Heroku and others fit the serverless paradigm.

To me serverless is about automatic scaling of performance and cost.

With Heroku you need to provision capacity in advance, and you pay for it whether you use it or not. Heroku doesn't scale automatically either, you do that manually.

[nailer]

Exactly. This is a massive misunderstanding of what serverless is. I came here to write 'no, no, no' but you already have.

> Serverless container services such as Heroku, ... AWS ECS/EKS Fargate, Google Kubernetes Engine, and Azure Kubernetes Service provide you with an environment where you can build a container

Not building or managing a container is why you're using serverless.

[mping]

Heroku does have autoscale capabilities based on avg response time. You set a min and max dyno count and off you go. It's as simple as it sounds but for run of the mill, follow-the-daytime apps it works.

[pier25]

As long as you're already provisioning a pro dyno which starts at $250.

[mping]

Didn't know, thanks. I was on an enterprise account.

[k__]

As far as I know Netlify is just a pretty wrapper around AWS services like Lambda, so I think, it should fit the serverless bill.

But I don't know much about their pricing.

[pier25]

Yeah, sorry, I wasn't clear about which of those I meant.

Netlify does definitely fit the serverless paradigm.