Hacker News new | ask | show | jobs
by smt88 3658 days ago
> Curious how much burden this makes for providers though

If those providers document their APIs using the Swagger format, there are tools that will automatically generate SDKs in tons of popular languages. The burden is nearly zero.

2 comments

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?
> Does that count as an SDK?

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.

Good point, think they are broadly used? My experience with the SDK generation has been hit or miss but the intention is good!
We use the SDK generators at my company, and our partners use the SDKs. They seem to work fine.

If you get into some edge cases, it can be trickier, but it's easy to parse Swagger docs and generate your own SDK from the docs themselves.