Amazon Web Services Inc. (AWS), has taken another step towards developing an official SDK to support the Go programming language by releasing a developer preview.
AWS has released the initial SDK project, which it purchased from another company, in an experimental phase. As the project nears its official release, AWS invites more developers to play with it and give feedback. This will allow them to join the ranks of supported SDKs like Java, C# Ruby, Python and JavaScript, PHP, and Objective-C.
Wikipedia describes Go as “a statically-typed language with syntax loosely deriving from that of C. It also adds garbage collection, type safety and some dynamic-typing capabilities. There are also additional built-in types like variable-length arrays, key-value maps and a large standard repository.”
AWS purchased a third-party SDK from Stripe. AWS then moved it to GitHub as an experiment project. This allowed developers to collect feedback, harden APIs and increase test coverage.
Moon continued his post in March with another post, where he explained that the project had reached another milestone when the “developer” and “master” branches were merged on GitHub.
Moon stated, “At this point, the SDK’s interfaces and architecture include the initial set of key improvements we had envisioned. We’re excited to announce progress and invite customers to test it again.” We will continue to collect and respond to your valuable feedback and work on further improvements, including better documentation and usability features.
Moon yesterday stated that Moon’s work on improving documentation paid off. The new developer preview now includes a Getting Started guide.
Moon stated that “Since our previous announcement, we’ve added a concurrent streaming download and upload manager for Amazon S3 and built-in support to response pagination with resource waiter support in work.”
Moon also stated that the project is currently in developer preview and that new updates will be released as soon as they are available.
Moon stated that the Developer Preview cycle’s goal is to get feedback on what works and what doesn’t so we can make tweaks before locking down API for stable 1.0.
