{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/live.nodejs.org/issues/32","repository_url":"https://api.github.com/repos/nodejs/live.nodejs.org","labels_url":"https://api.github.com/repos/nodejs/live.nodejs.org/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/live.nodejs.org/issues/32/comments","events_url":"https://api.github.com/repos/nodejs/live.nodejs.org/issues/32/events","html_url":"https://github.com/nodejs/live.nodejs.org/issues/32","id":144484463,"number":32,"title":"API Publishing with Node.js (Beijing)","user":{"login":"shiya","id":3713384,"avatar_url":"https://avatars.githubusercontent.com/u/3713384?v=3","gravatar_id":"","url":"https://api.github.com/users/shiya","html_url":"https://github.com/shiya","followers_url":"https://api.github.com/users/shiya/followers","following_url":"https://api.github.com/users/shiya/following{/other_user}","gists_url":"https://api.github.com/users/shiya/gists{/gist_id}","starred_url":"https://api.github.com/users/shiya/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shiya/subscriptions","organizations_url":"https://api.github.com/users/shiya/orgs","repos_url":"https://api.github.com/users/shiya/repos","events_url":"https://api.github.com/users/shiya/events{/privacy}","received_events_url":"https://api.github.com/users/shiya/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/live.nodejs.org/labels/Beijing","name":"Beijing","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-03-30T07:16:38Z","updated_at":"2016-04-12T03:29:58Z","closed_at":null,"body":"I'd like to give a talk on some aspects of API publishing/management using Node.js. Working for a company that publishes APIs that comes from many business models(Autodesk), organizing APIs to publish to internal and third party developers to consume was a big task. We have been heavily dependent on some great features of Node.js to streamline the process.\r\nI thought it'd be nice to share with others about my finding and generate some discussions so we can learn from others too.\r\n\r\nHere's an outline of what it's going to be about:\r\n- What are APIs and why they're important to companies\r\n- Why Node.js is the best technology for working with REST APIs\r\n  - Internal tools\r\n  - Sample code\r\n- The process of bringing APIs from different services and different languages all in one developer portal\r\n- Best practices, what worked for us, what didn't\r\n- Explorations on using npm packages as SDKs"},"comment":{"url":"https://api.github.com/repos/nodejs/live.nodejs.org/issues/comments/208687256","html_url":"https://github.com/nodejs/live.nodejs.org/issues/32#issuecomment-208687256","issue_url":"https://api.github.com/repos/nodejs/live.nodejs.org/issues/32","id":208687256,"user":{"login":"xeodou","id":914595,"avatar_url":"https://avatars.githubusercontent.com/u/914595?v=3","gravatar_id":"","url":"https://api.github.com/users/xeodou","html_url":"https://github.com/xeodou","followers_url":"https://api.github.com/users/xeodou/followers","following_url":"https://api.github.com/users/xeodou/following{/other_user}","gists_url":"https://api.github.com/users/xeodou/gists{/gist_id}","starred_url":"https://api.github.com/users/xeodou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xeodou/subscriptions","organizations_url":"https://api.github.com/users/xeodou/orgs","repos_url":"https://api.github.com/users/xeodou/repos","events_url":"https://api.github.com/users/xeodou/events{/privacy}","received_events_url":"https://api.github.com/users/xeodou/received_events","type":"User","site_admin":false},"created_at":"2016-04-12T03:29:58Z","updated_at":"2016-04-12T03:29:58Z","body":"Thanks for your advice @hackygolucky \r\n@shiya  That's awesome.  \r\nWe can talk more when we met in Beijing @shiya @hackygolucky "}}