[newrotik]

The point the article raises is whether those "non-FAANG engineers" should be using serverless at all.

Will their requirements ever scale to a point where it actually makes sense for them to be deployed as serverless services?

[pjerem]

> Will their requirements ever scale to a point where it actually makes sense

And even that. Let’s treat scaling issues latter. Create something that can be scaled horizontally dumbly, like a monolith you can run on n servers so you can scale without loosing money and then scaling can become your problem.

And that’s probably never if you are b2b like a majority of companies, since your usage depends and can be predicted from your sales team performance.

[arvinsim]

It's a chicken and egg problem.

How would you gain professional experience in something that is out of your current scope?

For example, if a frontend web developer wants to pivot to backend using serverless.

[closeparen]

mod_php is a serverless compute platform. The better question, will anyone’s requirements ever scale to a point where it makes sense for them to NOT be deployed as a serverless service? FTPing source code to a shared hosting provider is about as simple a deployment story as it gets; people bring all kinds of incredible complexity and thousands of hours of work on themselves messing with daemons, init scripts, systemd units, VM images, containers, schedulers, etc.

[lmz]

I guess you could pretend mod_php serverless until it needs to be load balanced and then it turns out the code actually relies on writing to the filesystem...

[weq]

So by No-FAANG engineer, you mean someone who isnt a robot ad hawker sell out?

Serverless allows anyone to be scale for minimal up-front cost and only pay for the usage they really need.

So glad that FAANG attract all this rare talent so us no-FAANG engineers can make a buck.

[lelanthran]

> So by No-FAANG engineer, you mean someone who isnt a robot ad hawker sell out?

Come now, is there any reason to throw those insults?

[Annatar]

Many.