So I disagree with that statement on debugging. Debugging a container is no less challenging than a function or serverless components. Traceability and observability principles apply to both and make either option possible.
Local development as well is easily achieved with serverless in the build and dev process.
Additionally, the user doesn’t wait long enough on a cold start these days enough to offset the gains that are possible in other areas by going with functions. But as with anything, there is no one perfect approach. I’m a big fan of containers as well. The answer always depends. But by not embracing a single cloud provider you miss out on a ton of benefits. And unless you are an ISV my opinion is that it’s not worth missing them
I've been using AWS lambdas long enough to know the difference between hosting my apps on classic managed and self-managed VMs as well as containers and serverless.
Serverless is great for small things, for automation, it could be a good option for internal tools. It can also be a good option when you do not expect a lot of traffic and your budget is very tight.
It's pretty bad when it comes to building bulletproof public facing real time apps (in comparison to other forms of hosting and development). It's possible, but other options allow you to develop and troubleshoot things simpler and faster.
I'm glad to have different opinions on this topic. I've been successfully building large Serverless Apps for a while now and couldn't be happier. I don't consider Lambda == Serverless so that umbrella to me includes things like SQS, SNS, Kinesis, DDB, EventBridge etc. Lambda is just a piece.
If I wanted < 5ms latency consistently, it's not my goto for things like that. So sure, a container and gRPC or another mechanism for communicating makes more sense. I might not even choose something Event-Driven in that case.
Simpler and faster ... again just opinions. Love the dialogue though and thanks for weighing in :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So I disagree with that statement on debugging. Debugging a container is no less challenging than a function or serverless components. Traceability and observability principles apply to both and make either option possible.
Local development as well is easily achieved with serverless in the build and dev process.
Additionally, the user doesn’t wait long enough on a cold start these days enough to offset the gains that are possible in other areas by going with functions. But as with anything, there is no one perfect approach. I’m a big fan of containers as well. The answer always depends. But by not embracing a single cloud provider you miss out on a ton of benefits. And unless you are an ISV my opinion is that it’s not worth missing them
What is ISV?
I've been using AWS lambdas long enough to know the difference between hosting my apps on classic managed and self-managed VMs as well as containers and serverless.
Serverless is great for small things, for automation, it could be a good option for internal tools. It can also be a good option when you do not expect a lot of traffic and your budget is very tight.
It's pretty bad when it comes to building bulletproof public facing real time apps (in comparison to other forms of hosting and development). It's possible, but other options allow you to develop and troubleshoot things simpler and faster.
ISV = Independent Software Vendor.
I'm glad to have different opinions on this topic. I've been successfully building large Serverless Apps for a while now and couldn't be happier. I don't consider Lambda == Serverless so that umbrella to me includes things like SQS, SNS, Kinesis, DDB, EventBridge etc. Lambda is just a piece.
If I wanted < 5ms latency consistently, it's not my goto for things like that. So sure, a container and gRPC or another mechanism for communicating makes more sense. I might not even choose something Event-Driven in that case.
Simpler and faster ... again just opinions. Love the dialogue though and thanks for weighing in :)