upvote
As a developer who spent a couple months developing a microservice using aws lambda functions:

it SUCKS. There's no interactive debugging. Deploy for a minute or 5 depending on the changes, then trigger the lambda, wait another 5 minutes for all the logs to show up. Then proceed with printf/stack trace debugging.

For reasons that I forgot, locally running the lambda code on my dev box was not applicable. Locally deploying the cloud environment neither.

I wasn't around for the era but I imagine it's like working on an ancient mainframe with long compile times and a very slow printer.

reply
I've witnessed developers editing Lambda code live in the AWS console. It is extremely painful to watch.
reply
Lol exactly
reply
Cloud Run is one service where GCP really shines. It is very flexible: handles services and long running background jobs, less annoying run time limitations like you find in Lambda.
reply
deleted
reply