pavolt

> I've apparently been using serverless since I started programming as a full-time career 10 years ago!

You have indeed.

As I mentioned above , S3 is a serverless service.

Last time I checked , you don't provisioned , partition or scale S3 this is done by AWS behind the scene.

Same for Firebase , same for many services.

Now the move is into the "compute" aspect of thing and the architecture.

Lambda basically replace, in a limited way , the compute aspect of your architecture (EC2) but obviously it has it's limits.

There is a confusion between "Serverless Framework" which is an automation of Lambda + API Gateway + CloudFormation , and "Serverless Computing" which is basically an "event driven" , "pay per execution" , "auto scaling / self healing" architecture.

> Serverless is a latest heavily marketed fad.

Serverless is the future of the Industry.

Lambda is not Serverless , it's just a FaaS which is a component of an entire Serverless Architecture.

Most specifically the majority of services provided by AWS and in the Cloud already are Serverless :

- Pay per usage ( GB , Execution , API Call )

- No Scaling or Provisioning ( SQS , CloudFront , Firebase )

- High Avaibility by default ( SQS , CloudFront , Firebase )

- Auto Scaling by default ( Azure CosmosDB , Firebase )

- Little to no technical limits for the service ( GCloud DataStore , S3 etc... )

If you have very little knowledge about something you shouldn't criticize it , that make you sounds even more ignorant.

Most of the stuff that people actually use on AWS (S3 , CloudFront , SQS , SNS ) are delivered with a serverless architecture in mind.

Again , if you are thinking "Lambda === Serverless" you really need to read more about this topic.