What can we expect from AWS SDK Go?

With Amazon’s latest announcement to deliver a new AWS SDK to Go-using customers, we asked expert contributor Chris Moyer to weigh in on the news.

Amazon is a true leader in reactive development. When they see a customer need for something, they work to improve...

it. It's another classic example of Amazon listening to the community and reacting to customers needs.

While most companies try to anticipate what customers will want to do, or build things that they themselves need, Amazon goes a step further and puts something out they think will be useful and then reacts to actual usage of the product. This acquisition of the golang SDK for AWS is another example of that. They did the same with the Python SDK a few years ago when they brought on my former boss Mitch Garnaat into AWS to make boto the official SDK for AWS and Python. In both cases, Amazon saw a significant opportunity to improve developers workflow by making the libraries used to connect to AWS better and easier to use.

This specific acquisition may be slightly more interesting because Go was developed by Google, and originally centered mostly around Google's Cloud Infrastructure. Still, Go is a great and fast programing language that many developers have started switching to. It's very similar to Node.js in syntax and design style, but in some tests appears to be significantly faster. With the addition of an official AWS API to Go, it also helps validate the language as a first-class programming language, something that benefits Google as well.

A few months ago when I was researching a new programming language to migrate many of our new applications over to, I ran across both Go and Node.js. We ended up choosing Node.js almost entirely because Go did not have an official AWS SDK. If we had waited to make the switch until now, that choice may have been different (it certainly would have been a lot harder to make).

Dig Deeper on AWS tools for development