|
|
|
|
|
|
by allthingsapi
3660 days ago
|
|
|
Does that count as an SDK? - simple code generation out of a spec? - Most SDKs exist because the provider is hiding some ugly code or making a number of primitive API calls to assemble the response. Aren't we falling back into the old "software" practices and now have to maintain code for anyone that users our service? - wasn't it supposed to be a service? |
|
|
A lot of big companies publish what they call an SDK, which is really just a thin, idiomatic wrapper on top of HTTP calls. Most of the AWS SDKs are like this, and sometimes the wrapper is way too thin (see: the disastrous mess that is the Dynamo JS library).
Should SDK mean more than that? I don't know. Is that kind of SDK useful? Definitely! HTTP is untyped, slow, and potentially tricky to use (like with OAuth 1.2), so it's nice to have some native code that abstracts that stuff away.