JSFoo 2012

It’s like kung fu with JavaScript and objects! All about building full size apps in JavaScript.

Aggregate your API's with ql.io and Node.js

Submitted by Prasanna Annamalai on Friday, 7 September 2012

Section: Server-side Technical level: Beginner Session type: Lecture

Abstract

1) How to deploy and use the service? 2) How to use the language to wrap endpoints and query / mashup data? 3) How to add Node.js hooks into the HTTP request / response process to control the data transferring between the server and endpoint? 4) Tools and repositories that extend ql.io with visualization capabilities and add new default data sources?

Outline

Today most of the Applications mashup API's from internal / external sources to produce data for querying, personalization etc., This leads to increased API inter-dependencies, multiple network round trips etc., ql.io addresses these developer pain points to declare API calls, fork and joins, filters and projections. ql.io significantly reduces the amount of code written to do API integration.

Speaker bio

A technology Enthusiast, I lead and run the external Developer Tools team for eBay Inc., Recently bitten by the Node.js bug.

Comments

  • Kamal Govindraj (@gkamal) 7 years ago

    Is having some basic idea of node.js a prerequisite for this talk? or is it something that is used to implement ql.io and not exposed to the client?

    What is your experience with ql.io? Have you contributed to it? Have you used it to build something in production? Are you exploring it? or you choose it as it sounded interesting and are going to prepare a talk around it?

  • Prasanna Annamalai Proposer 7 years ago

    Kamal, node.js is required only from running the ql.io perspective. To answer your other questions I haven’t done contributions to ql.io yet but have been actively following it on the github. I have been using it mainly from an internal tools perspective.

  • Kamal Govindraj (@gkamal) 7 years ago

    Thank you.

Login with Twitter or Google to leave a comment