Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloud Functions: Go 1.11 is now a supported language

cloud.google.com

Post reply on HN
Print view View original

31–40 of 107 posts

Re: Cloud Functions: Go 1.11 is now a supported language

#31

Post by chrisbroadfoot »

askver wrote: post #23
stewart27 wrote: post #8

Earlier quoted context omitted.

Cloud Functions PM here. I can give some insight: * 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 Func…

Does this effort take you closer to the (supposed) goal of running arbitrary X86/ARM Linux binaries as cloud functions, or is that a completely different direction?

At the sandboxing level, it's already possible (you can upload any binary and fork/exec it from one of the supported languages). That's made possible by gVisor, which is the underlying sandbox technology used in GAE and GCF.

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.

Re: Cloud Functions: Go 1.11 is now a supported language

#32

Post by pjmlp »

sethvargo wrote: post #28
pjmlp wrote: post #27

> func F(w http.ResponseWriter, r *http.Request) And me thinking the days of C compilers with 10 character limit for identifiers on the symbol table was long gone.

You can name the function anything you’d like. When you deploy the function, you specify the entry point function name. Many of our alpha testers used “F” for function because it’s quick and easy, but that’s not a requirement :)

That is a lame excuse for a blog with examples that are just bad engineering practices.

You surely don't have such examples with the other programming languages supported on the Google Cloud.

Re: Cloud Functions: Go 1.11 is now a supported language

#33

Post by pstuart »

sjeanpierre wrote: post #15
stewart27 wrote: post #8

Earlier quoted context omitted.

Cloud Functions PM here. I can give some insight: * 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 Func…

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?

Maybe Google Native Client support?

https://github.com/golang/go/wiki/NativeClient

Re: Cloud Functions: Go 1.11 is now a supported language

#34

Post by bdibs »

sethvargo wrote: post #2

Hey all - Seth from Google here. We're really excited to bring Go to Google Cloud Functions (GCF). Please try it out, give us feedback, and let us know if you have any questions!

Hey Seth, I was wondering if you guys ever discussed the previous AWS vs GCP performance post that was on here a while back.

Re: Cloud Functions: Go 1.11 is now a supported language

#35

Post by chrisbroadfoot »

w8rbt wrote: post #24
sethvargo wrote: post #2

Hey all - Seth from Google here. We're really excited to bring Go to Google Cloud Functions (GCF). Please try it out, give us feedback, and let us know if you have any questions!

I think AWS Lambda supports Go 1.x. Does GCF plan to stick to Go 1.11.x or broaden support to other Go versions in the future? What will happen to 1.11.x support when 1.12 comes out?

We use unpatched langauge toolchains/runtimes for GCF and second-generation GAE. That means a drastically reduced time to release for new language versions. (Maintaining patched runtimes was a significant burden to making new versions of Go available on GAE.)

For long-term support of various languages, see the GCP deprecation policy: https://cloud.google.com/terms/deprecation

Especially this sentence: "excluding [...] support for a programming language version that is no longer publicly supported by, or receiving security updates from, the organization maintaining that programming language"

So, that means we're committed to supporting the two most recent major version releases of Go, as per the Go release policy: https://github.com/golang/go/wiki/Go-Release-Cycle#release-m...

Disclaimer: I work on GCP and used to work on Go language releases.

Re: Cloud Functions: Go 1.11 is now a supported language

#36

Post by chrisbroadfoot »

pstuart wrote: post #33
sjeanpierre wrote: post #15

Earlier quoted context omitted.

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?

Maybe Google Native Client support? https://github.com/golang/go/wiki/NativeClient

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.

Re: Cloud Functions: Go 1.11 is now a supported language

#37

Post by sethvargo »

jay_kyburz wrote: post #30

As an aside, and since there are some googlers here, the heading animation on the blog has some issues in Firefox. They are super annoying. Would be nice if google supported all browsers. https://photos.app.goo.gl/MgsfH8GZndCdyBjeA

I’ll raise it with the team thanks!

Re: Cloud Functions: Go 1.11 is now a supported language

#38

Post by sethvargo »

bdibs wrote: post #34
sethvargo wrote: post #2

Hey all - Seth from Google here. We're really excited to bring Go to Google Cloud Functions (GCF). Please try it out, give us feedback, and let us know if you have any questions!

Hey Seth, I was wondering if you guys ever discussed the previous AWS vs GCP performance post that was on here a while back.

We worked with the original authors and they updated their original benchmarks. We are still compiling data and running our own benchmarks in other areas. Things were on pause for a bit as many Googlers took time off for the holidays to spend time with friends and family. I’ll check in on the team though. Thanks for the reminder!

Re: Cloud Functions: Go 1.11 is now a supported language

#39

Post by sethvargo »

pjmlp wrote: post #32
sethvargo wrote: post #28

Earlier quoted context omitted.

You can name the function anything you’d like. When you deploy the function, you specify the entry point function name. Many of our alpha testers used “F” for function because it’s quick and easy, but that’s not a requirement :)

That is a lame excuse for a blog with examples that are just bad engineering practices. You surely don't have such examples with the other programming languages supported on the Google Cloud.

Thank you for the feedback. We do have similar examples for the other programming languages because that’s what the community uses most frequently.

You’re still free to name the entry function whatever you prefer to match the styles and engineering practices of your organization :)

Post reply on HN