High Performance API Mashups with Node.js and ql.io
•Download as PPTX, PDF•
3 likes•2,685 views
This document discusses using ql.io and Node.js to create high performance mashups. It introduces ql.io as a way to reduce workload, processing, documentation and code length when working with APIs. It describes how ql.io can increase performance by handling requests, errors and reporting. It also outlines how to set up a ql.io server, define data sources, include scripts and routes, and use Mustache templates with jQuery. Examples are provided for visualizing API data using API Masher and including external API tables.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to High Performance API Mashups with Node.js and ql.io
Similar to High Performance API Mashups with Node.js and ql.io (20)
More from Jonathan LeBlanc
More from Jonathan LeBlanc (20)
Recently uploaded
Recently uploaded (20)
High Performance API Mashups with Node.js and ql.io
- 1. High Performance Mashups Using ql.io and Node.js Jonathan LeBlanc Developer Evangelist (PayPal) Twitter: @jcleblanc | @PayPalDev Github: github.com/jcleblanc
- 3. ql.io: The Problem is API Overload
- 4. ql.io: Reducing Workload + Processing Reduced Documentation Reduced Code Length Reduced Result Syncing
- 5. ql.io: Increasing Performance (Requests)
- 6. ql.io: Error Handling and Reporting
- 7. ql.io: Open Standard Foundation
- 9. ql.io: Using the System Standalone Server / Web Endpoint Node.js App
- 10. Language: Defining a Data Source Include in Request Include in .ql Table
- 11. ql.io: The Test Console Test Console: http://ql.io/console
- 12. Language: Including Script Routes user = "jcleblanc"; slides = select * from slideshare where user="{user}"; twitter = select * from github.users where user="{user}"; return { "slides": "{slides}", "twitter": "{twitter}" } via route '/social' using method post;
- 13. Language: Using Script Routes curl --header "content-type: application/x-www-form-urlencoded" -d "user=jcleblanc" http://localhost:3000/social
- 16. Example: jQuery for Cross Domain Reqs
- 17. Let’s Do It!
- 18. Tools: API Masher Visualization Engine: https://github.com/jcleblanc/api-masher Technology Backbone – ql.io – jQuery – Mustache Templates
- 20. Node.js: Installing the Package npm install ql.io-engine
- 21. Node.js: Including the Engine var Engine = require('ql.io-engine'); var engine = new Engine({ … });
- 22. Node.js: Invoking the Engine var script = "select * from …"; engine.execute(script, function(emitter){ emitter.on("end", function(err, res){ console.log(res['body'][0]); }); });
- 23. Tools: External API Tables Tables Source: https://github.com/jcleblanc/ql.io-tables https://github.com/ql-io/ql.io- site/tree/master/tables
- 24. Thank You! Any Questions? http://www.slideshare.net/jcleblanc Jonathan LeBlanc Developer Evangelist (PayPal) Twitter: @jcleblanc | @PayPalDev Github: github.com/jcleblanc
Editor's Notes
- Mashing up multiple data sourcesPerformance issues
- Language based on a SQL-like syntax which exports all data to JSON
- A create table call (to define a data source) may be included in the HTTP request to the ql.io web source or defined in a .ql file, which is added into the /tables directory of your application.
- create table slideshare on select get from "http://www.slideshare.net/rss/user/{user}" resultset "rss.channel";create table github on select get from "https://api.github.com/users/{user}";user = "jcleblanc";slides = select * from slideshare where user="{user}";person = select * from github where user="{user}";return { "slides": "{slides}", "person": "{person}"}
- Route files are also stored with the .ql extension but are placed under the routes directory
- First we need some mustache power
- Route files are also stored with the .ql extension but are placed under the routes directory
- -- http://api.hunch.com/api/v1/get-recommendations/?user_id=tw_jcleblanc&topic_id=cat_electronics&limit=5create table hunch on select get from "http://api.hunch.com/api/v1/get-recommendations/?user_id={uid}&topic_ids={tid}&limit={limit}" using defaults limit="20" resultset "recommendations";--select title from hunch where uid="tw_jcleblanc" and tid="cat_electronics";select * from finditems where keywords in (select title from hunch where uid="tw_jcleblanc" and tid="cat_electronics");