Back to all use cases

AssessmentSoftware / Digital Platforms

Go supports two major releases at a time, so a service on an older one gets no fixes

Engineering Platform Team

A typical engagement to move a fleet of Go services off a release that has left the supported window: read the release notes for each release in between, find the services that touch changed behavior such as encoding/json, net/http and removed GODEBUG settings, and plan the rollout.

Golang consulting

Overview

This is a typical engagement for a platform team whose Go services still build with Go 1.25. The Go project supports each major release until two newer ones exist, so 1.25 left support when 1.27 shipped. AceMQ and a partner Go specialist read the release notes for 1.26 and 1.27 against the team's code and write the upgrade plan.

Challenge

Go's compatibility promise covers the language, but behavior around it still changes between releases. Go 1.26 turned the Green Tea garbage collector on by default. Go 1.27 moves encoding/json onto the v2 implementation, which can change error text and rejects invalid UTF-8 and duplicate object names, makes net/http drain unread response bodies on close, which changes connection reuse, and removes several GODEBUG settings. A build that still carries a removed setting at an old value fails. Each service uses a different slice of these.

Environment

Several dozen Go services in a monorepo and a handful of separate repositories, a shared CI image with a pinned toolchain, go.mod files with different go and toolchain lines, container images built from the CI output, and services that call each other over HTTP and JSON.

Approach

AceMQ reads the release notes for each release between the current one and the target, then searches the code for the packages and settings they name: encoding/json options, response body handling, godebug lines in go.mod and //go:debug directives. Findings come first and no service is changed during the assessment.

Solution

  1. Lists the Go version, go line, toolchain line and godebug settings of every module
  2. Reads the release notes for 1.26 and 1.27 and records the changes that touch the services' code and dependencies
  3. Finds services that depend on encoding/json error text, invalid UTF-8 or duplicate keys, and on net/http connection reuse
  4. Finds removed GODEBUG settings that would fail the build and TLS settings that were removed
  5. Plans a canary on low-risk services with GC, latency and memory compared before and after
  6. Orders the rollout by risk, with a rollback to the previous build for each service and a toolchain upgrade routine for the next release

Outcome

The engagement delivers a module-by-module table of versions and settings, the list of changes that apply to each service, a canary plan with the metrics to compare, a rollout order with rollbacks and a routine for staying inside the two-release window. The team gets a plan it can schedule instead of upgrading whichever service breaks first.

Technologies

Go (Golang)DockerKubernetes

Ready for a Go (Golang) Health Check?

AceMQ's senior Go (Golang) engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.