# Why We Chose Go

DevFeed: [Why We Chose Go](<https://devfeed.tech/articles/why-we-chose-go-27987.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2020-03-02-whywechosego/>)

Author: Martin Mai Software; Site Reliability Engineer GitHub profile

Published: 2020-03-02T00:00:00Z

Content type: article

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [race-condition](<https://devfeed.tech/topics/race-condition.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [devops](<https://devfeed.tech/tags/devops.md>), [go](<https://devfeed.tech/tags/go.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [programming](<https://devfeed.tech/tags/programming.md>), [race-condition](<https://devfeed.tech/tags/race-condition.md>)

## AI overview

trivago explains why its team chose Go for a greenfield Recent Searches service. The article discusses Go's concurrency support and race detector in the context of a gRPC service running in Kubernetes and authenticated through OAuth2.

## Source excerpt

To the outside, trivago appears to be one single software product providing our popular hotel meta search. Behind the scenes, however, it is home to dozens of projects and tools to support it. T...