News for hackers. Stuff that matters.

A comment on The Evolution of SRE at Google. Parent comment

Re:The Evolution of SRE at Google by icedchai on Friday January 03, 2025 @05:51PM (#42590335)
In my experience, you are better off with ECS/Fargate than Lambda for serving an API. You get much more flexibility.

Also, I've witnessed people editing Lambda code through the console instead of doing a real deploy. what a mess...

[ Parent | on HN ]
Re:The Evolution of SRE at Google by scarface_74 on Friday January 03, 2025 @06:10PM (#42590465)
You can’t edit Lambda code in the console when you deploy a Docker image to Lambda.

As far as flexibility, while there have been third party libraries that let you deploy your standard Node/Express, .Net/ASP, Python/Flask app to Lambda, now there is an official first party solution

https://github.com/awslabs/aws-lambda-web-adapter

And as far as ECS, it is stupid simple

I’ve used this for years

https://github.com/1Strategy/fargate-cloudformation-example/...

[ Parent | on HN ]
Re:The Evolution of SRE at Google by mschuster91 on Friday January 03, 2025 @06:50PM (#42590780)
> Also, I've witnessed people editing Lambda code through the console instead of doing a real deploy. what a mess...

Yeah, exactly that's what I am talking about. Utter nightmare to recover from, especially if whoever set it up thought they needed to follow some uber-complex AWS blog post with >10 involved AWS services and didn't document any of it.

[ Parent | on HN ]
Re:The Evolution of SRE at Google by scarface_74 on Friday January 03, 2025 @07:57PM (#42591188)
You can’t edit Lambda code directly in the console when using Docker deployments
[ Parent | on HN ]