As a software architect, I hate serverless. Not because it doesn't work, but because it forces design constraints that cripple your application. Here's why always-on servers matter.
It sounds like the problem you describe is not with the concept of using serverless/faas cloud compute and adjacent services, but with the design and implementation done by some engineers you work with. That may be due to time constraints, lack of familiarity, engineering skill, or some other reason.
I’ve seen terrible containers, terrible vms, terrible bare metal servers. I’ve written good and bad myself. And yes, I’ve seen (and done) great implementation of serverless. It’s all just tools to be used.
Everytime I see serverless used - it’s always some illiterate frontender building next.js on lambdas. Always slow as molasses, always inflexible af.
It sounds like the problem you describe is not with the concept of using serverless/faas cloud compute and adjacent services, but with the design and implementation done by some engineers you work with. That may be due to time constraints, lack of familiarity, engineering skill, or some other reason.
I’ve seen terrible containers, terrible vms, terrible bare metal servers. I’ve written good and bad myself. And yes, I’ve seen (and done) great implementation of serverless. It’s all just tools to be used.