(no title)
stewart27 | 7 years ago
* We've been running a private early access preview/alpha since last August.
* This was our first compiled language on Cloud Functions, which came with its own set of challenges.
* It took us a while to find the right approach for supporting dependencies (both Go Modules and vendoring are supported). Unlike other providers, when you deploy your source code, Cloud Functions will automatically install dependencies listed in your go.mod file.
* Our testers gave us a ton of feedback that helped us polish the developer experience -- we identified and fixed many rough edges related to error messages during deployment/build and errors at runtime. Serverless products can be a bit opaque (since you can't just ssh into a machine), so getting this right is important.
I'd like to say that there was one big, interesting challenge that we had to tackle. But the reality is that we worked through many small details that only became apparent during testing. We wanted to address these so that we could offer a high quality experience for our public beta launch. We owe our alpha testers major credit for helping us find and solve issues.
Speaking of testers -- if you have feedback on the runtime, we'd love to hear from you in our Cloud Functions Beta Tester group [1].
[1] https://cloud.google.com/functions/docs/getting-support#beta...
sjeanpierre|7 years ago
Why wouldn't the binary be the deployed unit in this case?
ehsankia|7 years ago
pstuart|7 years ago
https://github.com/golang/go/wiki/NativeClient
vira28|7 years ago
stewart27|7 years ago
askver|7 years ago
chrisbroadfoot|7 years ago
As for making that an actual product, we're working on that, too. Sign up for the alpha here:
g.co/serverlesscontainers
Disclaimer: I work on GCP.