App Engine for Go now in General Availability

5979 views
Skip to first unread message

Jason Buberel

unread,
Jul 8, 2015, 11:25:55 AM7/8/15
to google-ap...@googlegroups.com

Today, we are announcing that Google App Engine for Go is now generally available. We're officially removing the "beta" label and extending App Engine's Service Level Agreement and Deprecation Policy to App Engine for Go.


Go is the cloud-native, open source language built to solve large-scale compute problems. Originally deployed as an experimental service in 2011, App Engine for Go has been serving production web and mobile applications for more than four years. In that time, the community has seen Go become the standard for cloud infrastructure technologies, including Docker and Kubernetes. App Engine for Go now serves millions of compute hours every month.


This announcement won't change how you use App Engine today, but we have heard your feedback: We will continue to make significant investments in App Engine for Go, including an improved SDK and an upgrade to the Go 1.5 runtime. Our goal is to make App Engine the best deployment platform for Go programmers.


For more information about App Engine for Go, see our complete online documentation.


-Jason Buberel, Product Manager, Go

Julius Kovac

unread,
Jul 8, 2015, 11:42:08 AM7/8/15
to google-ap...@googlegroups.com
Great news, thank you!

Ibrahim M. Ghazal

unread,
Jul 8, 2015, 12:28:21 PM7/8/15
to Jason Buberel, google-appengine-go
Does this mean the 'appengine' packages are set in stone now? I
thought the roadmap was moving to 'google.golang.org/appengine'
packages eventually?

Luna Duclos

unread,
Jul 8, 2015, 12:56:59 PM7/8/15
to google-ap...@googlegroups.com, jbub...@google.com
I would also very much like to know the intended direction of the appengine vs google.golang.org/appengine issue.

David Symonds

unread,
Jul 8, 2015, 1:34:59 PM7/8/15
to Luna Duclos, google-appengine-go, Jason Buberel
The intended path forward is that google.golang.org/appengine will be
the officially supported and recommended package library to use for Go
apps on App Engine, both for classic and Managed VM apps.

The "appengine" packages ("appengine", "appengine/datastore", etc.)
have been largely set in stone for years now. We've avoided making
backward incompatible changes to them since the go1 api_version was
released. That won't change, and code using them will continue to keep
working, but those packages will stop getting new features at some
point. We'll change docs to recommend the google.golang.org/appengine
packages at that time, but we want to reach parity there first (e.g.
aetest should work).

Stay tuned!

Wilson MacGyver

unread,
Jul 8, 2015, 3:22:36 PM7/8/15
to google-ap...@googlegroups.com
Great news! Good work

--
You received this message because you are subscribed to the Google Groups "google-appengine-go" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengin...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

nich...@noviumcollective.com

unread,
Jul 8, 2015, 3:24:15 PM7/8/15
to google-ap...@googlegroups.com
Just when we were about to ditch golang for our next App Engine project!

javie...@gmail.com

unread,
Jul 8, 2015, 3:24:15 PM7/8/15
to google-ap...@googlegroups.com
Yeah! Great work guys!

one...@gmail.com

unread,
Jul 8, 2015, 3:24:15 PM7/8/15
to google-ap...@googlegroups.com
Awesome! Keep up the great work.

Christopher Hesse

unread,
Jul 8, 2015, 9:50:26 PM7/8/15
to google-ap...@googlegroups.com, luna....@palmstonegames.com, jbub...@google.com
I noticed on this list here: https://github.com/golang/appengine in the section "Update code using deprecated, removed or modified APIs", it lists "appengine/socket" as deprecated, but using the net package on classic appengine produced an error when I tested it.  Should that be in the "not ported yet" section?

Glenn Lewis

unread,
Jul 8, 2015, 10:00:13 PM7/8/15
to Christopher Hesse, google-appengine-go
bcc: Jason, Luna

That list relates to APIs specifically for Managed VM (aka "v2") app usage.
"appengine/socket" will not be ported to Managed VM apps because the standard Go library can be used instead in that case.

We should probably split that list into two sections moving forward... "v1" vs "v2" status.
So for "v1" apps, there are several packages that have not been ported yet, and "appengine/socket" is one of them.
-- Glenn

--

cage....@gmail.com

unread,
Jul 9, 2015, 9:39:04 AM7/9/15
to google-ap...@googlegroups.com
Great news. No more Beta!!

mig...@persomi.com

unread,
Jul 9, 2015, 12:59:34 PM7/9/15
to google-ap...@googlegroups.com, ch...@pushbullet.com

But this means that to use sockets and deploy to Classic we still need to import "appengine", correct?

Ola Fosheim Grøstad

unread,
Jul 9, 2015, 2:52:16 PM7/9/15
to google-ap...@googlegroups.com
Thanks, this is great news!

Ola.

Greivin López

unread,
Jul 9, 2015, 2:52:16 PM7/9/15
to google-ap...@googlegroups.com
Great!

thatm...@gmail.com

unread,
Jul 9, 2015, 9:07:56 PM7/9/15
to google-ap...@googlegroups.com
Great to hear - just in time for my app to launch. https://downlist.io/ - very pleased with how it performs :)

David Symonds

unread,
Jul 9, 2015, 11:15:00 PM7/9/15
to mig...@persomi.com, google-appengine-go, Christopher Hesse
On 9 July 2015 at 09:29, <mig...@persomi.com> wrote:

> But this means that to use sockets and deploy to Classic we still need to
> import "appengine", correct?

Right now, yes. But you can use the google.golang.org/appengine
packages for almost all of your other app's functionality though.

Miguel Vitorino

unread,
Jul 10, 2015, 2:25:22 AM7/10/15
to David Symonds, google-appengine-go, Christopher Hesse

Yes, in fact we are using it for everything else. We were just hoping to remove that last bit.

david.a...@gmail.com

unread,
Jul 10, 2015, 12:02:11 PM7/10/15
to google-ap...@googlegroups.com
Glad to hear this! Any updates on completing the search API? Been waiting on this for a while: https://github.com/golang/appengine/blob/master/search/search.go#L484


On Wednesday, July 8, 2015 at 9:25:55 AM UTC-6, Jason Buberel wrote:

Brandon Thomson

unread,
Jul 11, 2015, 3:15:12 AM7/11/15
to google-ap...@googlegroups.com
What wonderful news! Also glad to hear that the "appengine" packages ("appengine", "appengine/datastore", etc.) will remain available for the forseeable future.

Dave Day

unread,
Jul 20, 2015, 2:17:12 AM7/20/15
to david.a...@gmail.com, google-appengine-go
On 11 July 2015 at 01:54, <david.a...@gmail.com> wrote:
Glad to hear this! Any updates on completing the search API? Been waiting on this for a while: https://github.com/golang/appengine/blob/master/search/search.go#L484

Those two features of the search API are now available in the managed VMs repo (see https://godoc.org/google.golang.org/appengine/search#SearchOptions). They should be available in an upcoming classic App Engine SDK.

Vincent Callanan

unread,
Aug 28, 2015, 7:44:06 AM8/28/15
to google-appengine-go, david.a...@gmail.com
Great News,

This beta tag was a serious "perceived" obstacle.
It forced me to shelve two projects in the past.

One related question regarding the upcoming release for Go 1.5 as flagged by the OP

Garbage collector concurrency/pause times is an important issue in long-running processes.
It is not ideal having to rely on concurrent compute instances to mitigate GC pause times.

I am wondering if the GOMAXPROCS restriction will be lifted in AppEngine run-time at least to accommodate the GC.

Thanks,
Vincent
Reply all
Reply to author
Forward
0 new messages