3 ms·

First off, thanks for the overview text. I really hate how many tech people just assume ‘you’ know what they mean because ‘they’ know what they mean. It’s like

First off, thanks for the overview text. I really hate how many tech people just assume ‘you’ know what they mean because ‘they’ know what they mean. It’s like they’re trying to accentuate the autistic stereotypes! >Pretty much what I have wanted since I first started learning about Docker. Why? I have a use for lambdas in an application I’m working on. But I don’t really get why you want stateless containers that spool up and down on demand. Is it for things like “I need this entire existing program to run and can’t refactor it to a lambda itself”? I only need to do some API processing and data we work, so I’m not entirely sure what starless containers are for. Might be a dumb question!

ec109685 8y ago
Go Cloud Run: https://cloud.google.com/run/docs/quickstarts/build-and-deploy https://cloud.google.com/run/docs/quickstarts/build-and-depl... Vs. Go Lambda: https://docs.aws.amazon.com/lambda/latest/dg/go-programming-model-handler-types.html https://docs.aws.amazon.com/lambda/latest/dg/go-programming-... The Cloud Run steps aren't that complex and you get something you can easily run on your local computer too.
- aynsof 8y ago
  You can definitely run Lambda functions locally, too: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html https://docs.aws.amazon.com/serverless-application-model/lat...
  - ec109685 8y ago
    Good point. Though you still have “the cloud” calling your function versus truly having everything local.