Hacker News Reader

In that sense, any 3rd party API, e.g. Stripe, or whatever, is "serverless" from the standpoint of the developer using it, but I doubt many would think of it that way.

That may change. S3, for example, is a building block for applications and abstracts away servers completely from the developer.

As do the following:

* SQS

* SNS

* DynamoDB

* Step Functions

* Lambda

* API Gateway

* CloudWatch Logs

* Cognito

* DynamoDB

You can build entire applications with the services above and never have to bother managing instances. It's not just about running code.

You can't upload your own code to the stripe API.

Someone else manages your containers and you manage the code.

… which means that you have much less control and when something goes wrong, you can't fix it.

To be clear, I enjoy having this as a tool available but not every problem is the same and not every organization is the same.

I agree with you about that definition, but just to be clear the author disambiguates in this article and describes serverless to mean FaaS in the context of the article.