4 ms·

Is there a reason dependency management happens like this? We currently deploy Go Lambda functions in AWS with the help of the Serverless Framework and it just

Is there a reason dependency management happens like this? We currently deploy Go Lambda functions in AWS with the help of the Serverless Framework and it just uploads the cross compiled Binary and not the whole project. Why wouldn't the binary be the deployed unit in this case?

pstuart 8y ago
Maybe Google Native Client support? https://github.com/golang/go/wiki/NativeClient https://github.com/golang/go/wiki/NativeClient
- chrisbroadfoot 8y ago
  No, it's not related to this. GOOS=linux and GOARCH=amd64 for GCF deployments. The sandboxing technology used is based on gVisor. We're working on arbitrary binary deployments, you can sign up for that here: g.co/serverlesscontainers Disclaimer: I work on GCP.
ehsankia 8y ago
While it's a lot more work for them, and some may already have the infrastructure setup for deploying their own binary, I think having GCP handle the end-to-end there is more user friendly in general. I can quickly write a Cloud Function from any computer, without having to deal with setting up the tool chains. If you want to just run binaries, sounds like Cloud Functions isn't what you're looking for.