May 25, 2017
Related Articles (871)
Amazon has largely rewritten its AWS SDK for Java. Although it is a rewrite from 1.11.x, Amazon used the same JVM so that developers don't have to migrate an entire product over to 2.x. Amazon focused on consistency, immutability, and ease of use in the rewrite. 2.x includes many requested features.
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?