App Engine’s New Go 1.11 Runtime • Hacker News Board

Re: App Engine’s New Go 1.11 Runtime

#61

Post by chrisbroadfoot » Tue, Oct 16, 2018, 9:27 PM UTC

merb wrote: post #14

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.

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…

Notable, though, that this new runtime better supports connecting to Postgres instances through the unix socket (/cloudsql/).

(GCP Gopher)

Re: App Engine’s New Go 1.11 Runtime

#62

Post by warrentr » Tue, Oct 16, 2018, 9:28 PM UTC

steren wrote: post #52

warrentr wrote: post #42

Earlier quoted context omitted.

How long will the legacy App Engine APIs continue to work? Will they be removed before the runtime is GA? These new runtimes seem amazing (and fix a lot of problems), but we also lose a ton of functionality that made app engine so desirable (easy users auth, images api, built in email sending, search, cron, and others). It kind of feels like we've thrown the baby out with the bathwater.

(App Engine PM here) The App Engine APIs will be present in the Go 1.11 runtime when it goes GA and until it is turned down. We do not know exactly which future version of the runtime will stop supporting them. We are working on Google Cloud standalone products to replace most missing features (e.g. Cloud Scheduler for cron jobs). Not all of them are ready yet. App Engine APIs were great when there was no alternative…

Thanks for the explanation. It makes sense and hopefully replacements are generally available before we lose the old apis.

Re: App Engine’s New Go 1.11 Runtime

#63

Post by xaduha » Tue, Oct 16, 2018, 9:29 PM UTC

I haven't used GAE since early days, but I heard it supports Docker now. Why wouldn't I just use Docker with whatever runtime I want?

Re: App Engine’s New Go 1.11 Runtime

#64

Post by buss » Tue, Oct 16, 2018, 9:31 PM UTC

heromat wrote: post #53

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 just tried to use go111, but I get the following message: >[7] Access Not Configured. Cloud Build has not been used in project before or it is disabled. Enable it by visiting " rel="nofollow">https://console.developers.google.com/apis/api/cloudbuild.go... then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry. So go111 cannot be used without Cloud Build…

Ah, yeah, looks like you have to activate billing. You'll be solidly within the free tier, though, so you won't be charged.

Re: App Engine’s New Go 1.11 Runtime

#65

Post by chrisbroadfoot » Tue, Oct 16, 2018, 9:31 PM UTC

deckarep wrote: post #40

Does this new classic+ environment now supersede the Flex environment? I’m curious because now it’s seems like there are 3 solutions. Although I really like the simplicity of this solution and the modernizing from the constraints of true classic mode.

(GCP Gopher here)

If you can run within the standard environment, I'd suggest you do (but you should check pricing, etc to see if it suits). Especially if you want 0-1 scaling.

I migrated golang.org from standard to flexible a couple weeks ago, primarily because of increased control over the runtime (custom Docker image) and increased instance sizes (configurable memory, CPU past the App Engine limits, which caps out at 2 GB). See https://golang.org/issues/27205 if you want to read more.

Re: App Engine’s New Go 1.11 Runtime

#66

Post by XorNot » Tue, Oct 16, 2018, 9:32 PM UTC

Is this a GA product or still "beta"? Google's consistent announcement of products as available while in beta is getting annoying, because their SLAs for "beta" products are still 0 and thus impossible to be able to use in actual business applications.

Re: App Engine’s New Go 1.11 Runtime

#67

Post by chrisbroadfoot » Tue, Oct 16, 2018, 9:40 PM UTC

XorNot wrote: post #66

Is this a GA product or still "beta"? Google's consistent announcement of products as available while in beta is getting annoying, because their SLAs for "beta" products are still 0 and thus impossible to be able to use in actual business applications.

(GCP Gopher)

Yes, it's beta.

You're right - if you require an SLA, don't use beta products.

As per https://cloud.google.com/terms/launch-stages:

> Beta is the point at which we are ready to open a release for any customer to use. There are no SLA or technical support obligations in a Beta release, and charges may be waived in some cases. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases.

Re: App Engine’s New Go 1.11 Runtime

#68

Post by chrisbroadfoot » Tue, Oct 16, 2018, 9:42 PM UTC

xaduha wrote: post #63

I haven't used GAE since early days, but I heard it supports Docker now. Why wouldn't I just use Docker with whatever runtime I want?

(GCP Gopher)

We support custom images for the flexible runtime, but not for the standard runtime.

If you're as keen for that as I am, sign up here: http://g.co/serverlesscontainers

Re: App Engine’s New Go 1.11 Runtime

#69

Post by chrisbroadfoot » Tue, Oct 16, 2018, 9:44 PM UTC

buss wrote: post #64

heromat wrote: post #53

Earlier quoted context omitted.

I just tried to use go111, but I get the following message: >[7] Access Not Configured. Cloud Build has not been used in project before or it is disabled. Enable it by visiting " rel="nofollow">https://console.developers.google.com/apis/api/cloudbuild.go... then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry. So go111 cannot be used without Cloud Build…

Ah, yeah, looks like you have to activate billing. You'll be solidly within the free tier, though, so you won't be charged.

You can set a $0 limit on your billing account, too.

Re: App Engine’s New Go 1.11 Runtime

#70

Post by pkroll » Tue, Oct 16, 2018, 9:45 PM UTC

tomcam wrote: post #48

melling wrote: post #38

Earlier quoted context omitted.

Does anyone have numbers to compare? Go is a compiled language. Should perform much better. Python might be perfectly acceptable of course.

I would absolutely love those numbers too. Always wondered about the working set of a minimal program, and also one with database access.

Well, there's the Techempower benchmarks at: https://www.techempower.com/benchmarks/

You can go to the filter, turn off all languages but Go and Python, and get a general idea.

There's also the old Computer Benchmark Game, which should be taken with a whole barrel of salt: https://benchmarksgame-team.pages.debian.net/benchmarksgame/...