News for hackers. Stuff that matters.
Re:Apply HN: Brightwork – Making APIs More Intelligent by asimuvPR on Wednesday April 06, 2016 @10:57PM (#11444373)
I've built something similar. A generic API that abstracts away implementation details of many different APIs into a simple set of endpoints. From my experience:

1) What APIs has your team built before that qualifies them to build this?

2) How will you manage changes, bugs, and obscure documentation issues in the APIs that will be made available through you?

3) Will your API cache results from participating parties?

4) What language will the API be written in?

5) Regarding API access security: How will you handle access to multiple APIs for the same client when each API requires a different set of tokens?

6) What kind of security (aside from having an encrypted connection) will this system have?

Re:Apply HN: Brightwork – Making APIs More Intelligent by philtaylor on Thursday April 07, 2016 @01:10AM (#11444867)
Good questions, I have tried to answer them as simple and complete as possible.

1) I wrote my first API in 1998 to connect field agent laptops to DARPA's web interface for incident management. Been building distributed systems and APIS for private enterprise ever since. Unfortunately, this my first publicly available product.

2) A combination of things, lots of questions here. Major versioning will control access to new features or structural changes in features. Bugs will be patched as often and quickly as possible in a minor release. Obscure documentation problem will be blogged about and then linked into the BW docs. Registered users will receive communication about all the aforementioned items via email or inline in the BW dashboard as notifications.

3) No, at this time we will to support upstream API caching.

4) There are many subsystems involved in BW. Our core is written in NodeJS.

5) Every upstream API endpoint is tracked by BW, we keep audit and metric logs. Each endpoint that requires authentication will interact with Vault (https://www.vaultproject.io) for requesting and storing credentials.

6) There are multiple layers of security with BW. - SSL, to secure the wire - Network (public/private), the only publicly exposed system is the proxy. The proxy is responsible for all traffic in/out of BW. - App Token, All upstream API calls including BW services and 3rd party API services require authentication to the proxy using an app token. The app token is unique to each app you run on BW and using ACL security will allow access to only the services provisioned for that app (data, email, storage, user auth). - User Authentication/ACL, every BW account is secured from one another using ACL security. Audit logs are maintained for all requests made in BW. - Endpoint Security, as mentioned above if you are connecting to an upstream API endpoint that requires a token then BW will use Vault.

Thanks!

Re:Apply HN: Brightwork – Making APIs More Intelligent by asimuvPR on Thursday April 07, 2016 @06:14PM (#11451126)
The answer to the first question is really interesting. We spend so much time building software and have little to show. Its nice that you are taking the effort to build something like this. I for one think APIs are still very crude and need lots of love to evolve into something that we can use without waking up at 3AM on Wednesday because somebody pushed an update. :)
Re:Apply HN: Brightwork – Making APIs More Intelligent by josh_carterPDX on Thursday April 07, 2016 @06:25PM (#11451186)
Yes to all of this! :)
Re:Apply HN: Brightwork – Making APIs More Intelligent by asimuvPR on Thursday April 07, 2016 @07:46PM (#11451599)
We should email. I'm always researching new API patterns and having real feedback would be very beneficial. Email in profile. :)
Re:Apply HN: Brightwork – Making APIs More Intelligent by josh_carterPDX on Friday April 08, 2016 @12:17PM (#11455798)
Absolutely. I'll reach out. Thanks!