Why Go Is the Go-To Language for High-Concurrency Backend Services

1. Why Choose Go

As a backend developer the author compares PHP and Go, noting that while PHP (especially under php‑fpm) feels easy, it cannot handle the high‑concurrency demands of live‑streaming services. Go’s rising popularity at companies like Tencent, Baidu, and Didi, plus its concise syntax, make it a compelling alternative.

2. The Concurrency Challenge

In a live‑streaming scenario each user entering a room requires multiple pieces of data (version service, basic stream info, user profile, entitlement data, statistics, etc.). A PHP implementation would fetch these sequentially, causing the total latency to equal the sum of all individual calls.

Using Go, the same request can launch all fetches concurrently, so the overall latency equals the longest individual call.

3. Method 1 – sync.WaitGroup

// Request entry
func main() {
    var (
        VersionDetail, LiveDetail, UserDetail, EquityDetail, StatisticsDetail int
    )
    ctx := context.Background()
    GoNoErr(ctx,
        func() { VersionDetail = 1; time.Sleep(1 * time.Second); fmt.Println("执行第一个任务") },
        func() { LiveDetail = 2; time.Sleep(2 * time.Second); fmt.Println("执行第二个任务") },
        func() { UserDetail = 3; time.Sleep(3 * time.Second); fmt.Println("执行第三个任务") },
        func() { EquityDetail = 4; time.Sleep(4 * time.Second); fmt.Println("执行第四个任务") },
        func() { StatisticsDetail = 5; time.Sleep(5 * time.Second); fmt.Println("执行第五个任务") },
    )
    fmt.Println(VersionDetail, LiveDetail, UserDetail, EquityDetail, StatisticsDetail)
}

func GoNoErr(ctx context.Context, functions ...func()) {
    var wg sync.WaitGroup
    for _, f := range functions {
        wg.Add(1)
        go func(fn func()) { fn(); wg.Done() }(f)
    }
    wg.Wait()
}

4. Method 2 – errgroup Library

// Request entry
func main() {
    var (
        VersionDetail, LiveDetail, UserDetail, EquityDetail, StatisticsDetail int
        err error
    )
    ctx := context.Background()
    err = GoErr(ctx,
        func() error { VersionDetail = 1; time.Sleep(1 * time.Second); fmt.Println("执行第一个任务"); return nil },
        func() error { LiveDetail = 2; time.Sleep(2 * time.Second); fmt.Println("执行第二个任务"); return nil },
        func() error { UserDetail = 3; time.Sleep(3 * time.Second); fmt.Println("执行第三个任务"); return nil },
        func() error { EquityDetail = 4; time.Sleep(4 * time.Second); fmt.Println("执行第四个任务"); return nil },
        func() error { StatisticsDetail = 5; time.Sleep(5 * time.Second); fmt.Println("执行第五个任务"); return nil },
    )
    if err != nil { fmt.Println(err); return }
    fmt.Println(VersionDetail, LiveDetail, UserDetail, EquityDetail, StatisticsDetail)
}

func GoErr(ctx context.Context, functions ...func() error) error {
    var eg errgroup.Group
    for i := range functions {
        f := functions[i] // capture loop variable
        eg.Go(func() error { return f() })
    }
    return eg.Wait()
}

5. Closure Capture Pitfall

When a loop variable is referenced directly inside a goroutine, all goroutines capture the same variable, leading to unexpected results. The author demonstrates three variants:

Version 1 : Assign the loop variable to a new local variable ( f := functions[i]) before launching the goroutine – works correctly.

Version 2 : Use the range form with index ignored ( for _, f := range functions { fs := f; ... }) – also works because fs is a fresh copy.

Version 3 : Use the loop variable f directly inside eg.Go – fails, producing errors shown in the screenshot.

The failure occurs because the closure captures the reference to f, which after the loop ends holds the last function value. Creating a new variable inside the loop breaks this reference chain.

6. Additional Notes

Other third‑party libraries provide similar group‑execution functionality; they can be explored on GitHub, but the core concepts remain the same.

Overall, the article presents the fundamental Go concurrency patterns that split a parent task into multiple child goroutines, dramatically reducing latency for high‑throughput services.