Live data from Hacker News

Cloud Functions: Go 1.11 is now a supported language

cloud.google.com

21–30 of 107 posts

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

#21
post #12

Earlier quoted context omitted.

Thanks for the response. Would like to see more granular triggers (event types). Especially with Firebase. Also, would like to see more examples with firestore.

Which ones would you like to see? We're always looking for new use cases to support.

These are not specific to Go. firebase authentication -> user account from disabled to enabled. firebase authentication -> when a new phone number is associated. Firestore -> field level triggers. Right now we have only document level trigger.

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

#23
post #4

Earlier quoted context omitted.

As we all know, it took Google so long to get this. Can you overview on what are some of the technical challenges faced? Just curious. Thanks.

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?

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

#24

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?

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

#25
post #20

Earlier quoted context omitted.

> I'm curious how the implementation of Go has affected the ease of integrating other languages. In some ways, it helps. You start to see similar issues arise and know what to look out for when you're launching a new runtime. In other ways, every language has its peculiarities and its own set of design considerations. Launching/polishing a completely new language still takes a decent amount of work. Launching a new v…

Although I've never used Lambda Layers. Do you think a similar approach is something that could be implemented? Maybe even just something for compiled languages like Go, Crystal, etc that will just run the binary?

It's definitely something that we've discussed.

Would you consider running a container that could be run like Cloud Functions? This container could run the binary that you create. It's not something that we support today but I'm curious whether this would meet your needs.

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

#26
post #20

Earlier quoted context omitted.

Although I've never used Lambda Layers. Do you think a similar approach is something that could be implemented? Maybe even just something for compiled languages like Go, Crystal, etc that will just run the binary?

It's definitely something that we've discussed. Would you consider running a container that could be run like Cloud Functions? This container could run the binary that you create. It's not something that we support today but I'm curious whether this would meet your needs.

> running a container that could be run like Cloud Functions

Does this mean we actually run the container ourselves on our GKE cluster or in a VM? Or do you mean a "container" runtime for Cloud Functions? Both would be interesting, but we'd prefer the latter since there would be less to manage. I'd be interested to see the performance of it.

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

#28
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 :)

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

#29
post #24

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 will include support for more runtimes and language versions in the future.
Post reply on HN