3 ms·
Official, full support, instead of a custom implementation where it can take weeks to add support for a new service that's already a part of the C++ lib. Also,
by oomkiller 11y ago
Official, full support, instead of a custom implementation where it can take weeks to add support for a new service that's already a part of the C++ lib. Also, there are some newer languages out there that don't have quality libraries for AWS, but do have C extension support. This will allow wrappers for to be created so these languages can be used with AWS as well. Just take a look at how the Java lib is used.
- 15155 11y agoIn my experience, it's just easier to take their API descriptor file (JSON IIRC) and generate a client from it.
- ranman 11y agoThis is what boto3 does
- monksy 11y agoWouldn't that be WADL?
- Slippery_John 11y agoNo, WADL is XML. You can see some of the data files in the boto3 repository: https://github.com/boto/boto3/tree/develop/boto3/data https://github.com/boto/boto3/tree/develop/boto3/data It is somewhat similar in concept
- monksy 11y agoWADL is an description language for REST services.
- michaelmior 11y agoGiven that it is just an HTTP API, I'm not sure it would actually be that much faster to wrap a C++ API than just write a native lib. Plus unless the wrapper is written by Amazon as well, it's not really "official, full support."
- nathankunicki 11y agoI'm still not sure I follow. There are plenty of first-party fully supported SDK's for various languages, eg. Ruby, Node.js, Java, .NET, etc: https://aws.amazon.com/tools/ https://aws.amazon.com/tools/ In fact from personal experience of the Node one the SDK uses the API descriptor to generate the client (Which makes unit testing it tricky incidentally, but I digress).