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

App Engine’s New Go 1.11 Runtime

blog.golang.org

Post reply on HN
Print view View original

21–30 of 101 posts

Re: App Engine’s New Go 1.11 Runtime

#21

Post by Strom »

buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

> I'm the tech lead and primary software engineer on the Go runtime.

Hey thanks a lot for your efforts! Your direct communication about the Go runtime progress has been a breath of fresh air compared to the years preceding you. I wonder though, how many developers are there on the App Engine Standard Go team?

Re: App Engine’s New Go 1.11 Runtime

#22

Post by steren »

Strom wrote: post #20
buss wrote: post #18

Earlier quoted context omitted.

> I take it the datastore change is just an api change? (There isn't any data migration needed, is there?) Yup! > It looks like memcache is moving to a third-party service now instead of a built-in api. Is performance different? Does anyone have experience with this? I'm not sure about the performance impact. But I can tell you that we're working with the Cloud Memorystore team to have a better memcache story for the…

Both google.golang.org/appengine/datastore and cloud.google.com/go/datastore connect to the same data? Is there a list of incompatibilities somewhere? I remember seing some serialization differences between these two datastore libraries.

Hi (App Engine PM here). Yes both libraries connect to the same database (Cloud Datastore). cloud.google.com/go/datastore is preferred as it uses the Cloud Datastore API instead of the App Engine specific API, so your code will be portable.

You are right that the devil is in the details, and there might be some slight serialization differences. I cannot find an exact list.

Feel free to post here if you need more help.

Re: App Engine’s New Go 1.11 Runtime

#23

Post by throwaway9981 »

buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

is gRPC supported now or is that more of an upstream HTTP 1.1 constraint?

Re: App Engine’s New Go 1.11 Runtime

#24

Post by steren »

throwaway9981 wrote: post #23
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

is gRPC supported now or is that more of an upstream HTTP 1.1 constraint?

Hi (App Engine PM here) You can use any go package in the Go 1.11 runtime, including the ones relying on GRPC. Did I answer your question?

Re: App Engine’s New Go 1.11 Runtime

#25

Post by buss »

throwaway9981 wrote: post #23
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

is gRPC supported now or is that more of an upstream HTTP 1.1 constraint?

Inbound GRPC will be limited to HTTP1.1; that's a limitation of the platform rather than the language runtime. We're working on HTTP2 support, but I can't promise any timelines.

Re: App Engine’s New Go 1.11 Runtime

#26

Post by wiradikusuma »

buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

It's always been my impression that Go on GAE is the most lightweight compared to Java/Python, as it not "memory hungry" like Java nor "slow" like Python. Am I correct?

Re: App Engine’s New Go 1.11 Runtime

#27

Post by steren »

merb wrote: post #15
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

when will appengine support setting environment variables with gcloud command or inside the gcloud console instead of in the app.yaml, i.e. so that each environment can have their own variables without copying app.yaml's?!

(App Engine PM here) At this time, app.yaml is the only way to set env vars. If you want to separate environments, you could use different .yaml files, I personally use app.staging.yaml and app.prod.yaml

Re: App Engine’s New Go 1.11 Runtime

#28

Post by buss »

wiradikusuma wrote: post #26
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

It's always been my impression that Go on GAE is the most lightweight compared to Java/Python, as it not "memory hungry" like Java nor "slow" like Python. Am I correct?

It is quite lightweight, yes!

Though...I wouldn't necessarily call Python slow! Python keeps getting faster, and we now support Python 3.7 on our second gen runtimes: https://cloud.google.com/blog/products/gcp/introducing-app-e...

Re: App Engine’s New Go 1.11 Runtime

#29

Post by steren »

bpye wrote: post #5

This actually seemed to be live a week or two ago, I managed to run Miniflux [1] on App Engine with no changes though to get it working properly it would need it's scheduling changing. [1] - https://github.com/miniflux/miniflux

(App Engine PM here) Nice to hear! Yes indeed, we announced Go 1.11 on App Engine last week at Cloud Next London.

Re: App Engine’s New Go 1.11 Runtime

#30

Post by rhodysurf »

steren wrote: post #24
throwaway9981 wrote: post #23

Earlier quoted context omitted.

is gRPC supported now or is that more of an upstream HTTP 1.1 constraint?

Hi (App Engine PM here) You can use any go package in the Go 1.11 runtime, including the ones relying on GRPC. Did I answer your question?

You cant run a GRPC server though still right? Thats all I really want to be able to do especially now that the app engine endpoints libraries are no longer supported on python
Post reply on HN