5 ms·
> but I think what you’re missing is people are using lambda functions not just to run some image resizing function, but as their entire backend. Sometimes it
by rewmie 3y ago
> but I think what you’re missing is people are using lambda functions not just to run some image resizing function, but as their entire backend.
Sometimes it makes sense. I see people criticizing stuff they know nothing about.
I worked on a project where I had to put together a REST API for an internal project. After considering the traffic projections, we noticed a API Gateway + lambdas fitted quite neatly in the AWS free tier, and we did everything in lambdas. We also did a proof of concept in ECS and everything was far more complex and convoluted. With lambdas, the whole project consisted of a single CDK package which included also the nodejs code for the handlers.
In another project, we even skipped the API gateway and instead had a NLB invoke a couple of lambdas. It worked flawlessly, and in the free tier.
I'm seeing comments about the need to do engineering, but these same comments are outright clueless and fail to do the faintest cursory research. It's just people commenting on stuff they know nothing about with a demeaning tone. Not cool, not smart.
- rajamaka 3y agoYou're completely right, the only criticisms of serverless in this bizarre thread are from a complete lack of understanding or experience
- Maxion 3y agoI guess a lot depends on your developer costs, a docker in e.g. GCPs cloud run costs peanuts compared to a devs salary per month. IMO the less you need to code on top of your actual business logic functions - the better off you are for small projects. Docker is still one of the best options, as if your tiny app is somehow business critical you can easily migrate it to other infra. With lambdas you’re stuck on AWS.
- rewmie 3y ago> With lambdas you’re stuck on AWS. You're not getting stuck on AWS because you added a lambda to offload a background task, or because you implemented a low-traffic REST API with API Gateway. If you're rethinking where you deploy services, your decision won't factor in these irrelevant details. Odds are you are more concerned with S3 and CloudWatch than REST APIs.