>Don't get me started on things like authentication, file uploads and protecting your server from being DDoSed or driving up your cloud computing bill by someone creating expensive queries.
These are API Management requirements, and they require a different treatment from the traditional approach, just granting access and checking rate limits is not enough. One approach is to statically analyze the query and determine how it will affect your backend, and how much data it intends to retrieve. Products are starting to come into the market, recently IBM API Connect had this announcement about it: https://community.ibm.com/community/user/imwuc/blogs/rob-the...
Seems like Walmart is focusing on SDKs to handle visual objects like buttons in HTML and JS and for Mobile.
Good to see the community provide other SDKs but why the interest in a Python SDK?
There is something about curating the ecosystem - Apple puts great effort towards it, maybe not perfect, but certain rules are enforced. Who owns that music "skill"? aren't there others that you could used and replace the not so random one? can't you down-vote it? and help the community curate it?
In the past we would have formed a standards group, called all interested vendors, and each one would defend their turf, ultimately arriving to a compromise that almost no one used. This has evolved to offering flexibility to experiment and through real usage we may start seeing adoption of certain extensions and at some point it may make sense to adopt them, that makes more sense!
API Harmony was just added to the list - not just discovering the API but also relating the API to usage, SDKs, discussions, and other relevant information a developer may be looking for.
If I am going to trust you my API I want to know that you have top notch SLAs on your service, and since I am providing the code you are going to want to monitor the heck out of it so that you know that in case of failure whose fault it is.
I see you joining the bands of "serverless" computing - this is no easy feat - can you speak to what is in your backend and how you plan to support heavy workloads?
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?
As an API provider, would indexing and discovery of your APIs be of value to you?
As a developer with discovery may enable synthesis and composition of APIs.
Sites like ProgrammableWeb (http://www.programmableweb.com) and API Harmony (http://apiharmony-open.mybluemix.net) would do better if they could understand what changed and what is available.
I lead the API Harmony team at IBM Research and this information would be extremely valuable.
Like any data service, it will be as good as its data - without a big concerted effort to gather data it will soon die.
You need to reach out to science fairs, big and small, as well as Science Research programs and convince them to post their work here. Also in lieu of citations awards earned would help distinguish the more decent ones. Downloads may also be a good metric to measure interest
For external purposes - use stackoverflow
For internal purposes - you may need to deploy your own - phpBB used to be popular a few years back https://www.phpbb.com/