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

11–20 of 101 posts

Re: App Engine’s New Go 1.11 Runtime

#11

Post by buss »

bpye wrote: post #7
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…

Several of your links are broken, they have been elipsised.

Sorry, I copy pasted without double checking. Now fixed!

Re: App Engine’s New Go 1.11 Runtime

#12

Post by skybrian »

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 take it the datastore change is just an api change? (There isn't any data migration needed, is there?)

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?

Re: App Engine’s New Go 1.11 Runtime

#13

Post by selljamhere »

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…

Does the move to gVisor pave the way to connecting CloudSQL instances? The removed limitations sound like they were road blocks.

Re: App Engine’s New Go 1.11 Runtime

#14

Post by merb »

selljamhere wrote: post #13
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…

Does the move to gVisor pave the way to connecting CloudSQL instances? The removed limitations sound like they were road blocks.

you already could connect to cloudsql instances. however you needed a proxy, but not because of AppEngine, you need it because of security.

either you whitelisted your ips or you used the proxy (which go appengine could already use).

so with go you just needed to use https://github.com/GoogleCloudPlatform/cloudsql-proxy which means you just need to change the query string.

however a new feature is emerging where you can have a private ip that is connected to your internal services, however it is still a beta feature.

Source: myself, but not a googler, just a regular user

Re: App Engine’s New Go 1.11 Runtime

#15

Post by merb »

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?!

Re: App Engine’s New Go 1.11 Runtime

#16

Post by buss »

selljamhere wrote: post #13
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…

Does the move to gVisor pave the way to connecting CloudSQL instances? The removed limitations sound like they were road blocks.

For cloudsql in particular, you can connect via the `/cloudsql` Unix socket. But anything that needs raw socket access can now be used from App Engine.

See https://cloud.google.com/appengine/docs/standard/go111/using... and scroll way down to the sample code.

Re: App Engine’s New Go 1.11 Runtime

#17

Post by selljamhere »

buss wrote: post #16
selljamhere wrote: post #13

Earlier quoted context omitted.

Does the move to gVisor pave the way to connecting CloudSQL instances? The removed limitations sound like they were road blocks.

For cloudsql in particular, you can connect via the `/cloudsql` Unix socket. But anything that needs raw socket access can now be used from App Engine. See https://cloud.google.com/appengine/docs/standard/go111/using... and scroll way down to the sample code.

Awesome!

Re: App Engine’s New Go 1.11 Runtime

#18

Post by buss »

skybrian wrote: post #12
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 take it the datastore change is just an api change? (There isn't any data migration needed, is there?) 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 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 App Engine second generation runtimes

Re: App Engine’s New Go 1.11 Runtime

#20

Post by Strom »

buss wrote: post #18
skybrian wrote: post #12

Earlier quoted context omitted.

I take it the datastore change is just an api change? (There isn't any data migration needed, is there?) 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 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.
Post reply on HN