Hacker News new | ask | show | jobs
by my69thaccount 1481 days ago
1. It's trendy

2. It locks you in to a certain vendor

3. It costs more

1 comments

The lock-in part is increasingly untrue. Esp. if you are on gcloud, your functions are not tied to their infra at all. Eg. For nodejs you are just writing express middlewares with no real gcloud infra dependency. You can also use their build packs to run and test the functions locally. gcloud serverless infra is also built on knative so if you have teams with k8s familiarity you can run them on in-house infrastructure.

For AWS lambda I believe it was initially true, but now I believe they also support running arbitrary containers.

The costs more part is very much subject to nature of use case. If you have a lot of small services that are invoked once in a while you can benefit from serverless pricing.