[madflojo]

All good. There were a lot of factors to creating the list, Enterprise use and readiness was one big one. So we narrowed it down to what we thought were the best choices. Always the possibility we missed something, but thats true of any decision like this.

Appreciate the read and questions though!

[mikece]

Are you on the AMEX team(s) in question? I am always interested in knowing all of the factors that were part of the decision in why a team chose the language or platform it did and if, after a respectable period of time, everyone is still happy with the choice or if there's buyer's remorse and what greener pasture languages/platforms (or problems with the selected stack) are bringing on those second thoughts.

[madflojo]

Yeah, thoughts and opinions are my own of course but overall we've had good experiences.

I tried to insert some of the benefits we are seeing into the article in different pieces but now that we are several years later have it running in production. We are happy with the decision. In my opinion, there are even some newer things we didn't write in Go that I kind of wish we did.

The reasons we choose Go are holding true, and I can't say enough about how the performance and low GC times out of the box is something that is very beneficial. At least for my use cases.