Azure runtime stack for Go 1.19 flagged as Experimental

Question

Azure runtime stack for Go 1.19 flagged as Experimental

Terziev Ivan 0

I'd like to set up an App service using the Go 1.19 runtime stack. It has plentiful documentation and is relatively well fleshed out so it supports my use-case. However, it is flagged as experimental. I could not find any document saying why this is so. What is the reason for this? Is it safe to use the runtime stack in for production purposes?

Grmacjon-MSFT 19,151 Reputation points Moderator

2023-04-18T19:32:17.3666667+00:00

Hi @Terziev Ivan

Thanks for the question. We are checking internally with the engineering team to get more clarity on why its flagged as experimental and will get back to you when we hear back from them.

Best,

Grace
Dagoberto Rojas 90 Reputation points

2023-04-23T07:55:43.7733333+00:00

@Terziev Ivan I came across these two sources of information Running Go Applications on Azure App Service, which is outdated but leads to this page: Go available on App Service but the important information there is:

Support for Go is being added as an Experimental feature. Experimental features are work in progress and can radically change or completely disappear at any time. You can use it if you’re an early adopter, see something useful to you, and would like to help test the feature.

This is for App Service Linux, which is an image provided by Azure. But you could still use Go if you use a custom docker image either from docker hub or a private registry (Which if you want to use it for production would be the best way to go, here you could find more info about how to do so: Configure a custom container for Azure App Service ). Using App Service Linux comes with an easy configuration, but even if the feature can "completely disappear at any time" (not likely) you would probably get notified to take action before MSFT removes support for the feature.

1 answer

Your answer

Grmacjon-MSFT 19,151 Reputation points Moderator

2023-04-18T19:32:17.3666667+00:00

Hi @Terziev Ivan

Thanks for the question. We are checking internally with the engineering team to get more clarity on why its flagged as experimental and will get back to you when we hear back from them.

Best,

Grace
Dagoberto Rojas 90 Reputation points

2023-04-23T07:55:43.7733333+00:00

@Terziev Ivan I came across these two sources of information Running Go Applications on Azure App Service, which is outdated but leads to this page: Go available on App Service but the important information there is:

Support for Go is being added as an Experimental feature. Experimental features are work in progress and can radically change or completely disappear at any time. You can use it if you’re an early adopter, see something useful to you, and would like to help test the feature.

This is for App Service Linux, which is an image provided by Azure. But you could still use Go if you use a custom docker image either from docker hub or a private registry (Which if you want to use it for production would be the best way to go, here you could find more info about how to do so: Configure a custom container for Azure App Service ). Using App Service Linux comes with an easy configuration, but even if the feature can "completely disappear at any time" (not likely) you would probably get notified to take action before MSFT removes support for the feature.

Answer 1

Grmacjon-MSFT 19,151 Moderator

Hi @Terziev Ivan ,

Adding to Dagoberto's response- Go is currently in an experimental phase and not recommended for production applications. The Azure docs will be updated to reflect a change if Go becomes GA. If you want to use it in production, you can consider running your own custom container https://learn.microsoft.com/en-us/azure/app-service/quickstart-custom-container?tabs=dotnet&pivots=container-linux-vscode

Hope that helps.

-Grace

Grmacjon-MSFT 19,151 Reputation points Moderator

2023-04-27T18:39:20.95+00:00

Hi @Terziev Ivan

checking to see if the above responses help answer your question. Please remember to mark "Yes" if the answer was helpful so that others in the community facing similar issues can easily find the solution.

Thanks

-Grace

Share via

Azure runtime stack for Go 1.19 flagged as Experimental

1 answer

Your answer