API + Static Clients

Our thoughts about our departure from traditional Web development approaches in favor of static HTML5 and Javascript clients combined with RESTful JSON APIs.

Transcript

1. API + Static clients Challenging regular Web development approaches
2. Who the hell..? Ronan Berder খ۽ Makara Wang ԦߒӉ Wiredcraft http://wiredcraft.com
3. About you guys • Who here is building apps with node.js?
4. Concepts
5. Use cases • Static blog (Github pages) with dynamic data beyond comments. • Multiple clients (Web, mobile, tablet) with a single service.
6. Why RESTful • Not JSONP (not only GET) • Why?
7. What’s different?
8. Some stuff is hard • CORS (Cross-origin resource sharing) • Sessions
9. How to get around it • CORS: • Allow anything from anywhere... • Have the clients registered.
10. How to get around it • Session • Require CORS credentials being sent and manage sessions regularly • Manage sessions in a different way.
11. Show me the code! </>
12. Server side
13. CORS • cors.js • Express 3.x (http://expressjs.com/) • Debug (https://github.com/ visionmedia/debug)
14. Session • Express + connect-redis • Passport (http://passportjs.org/) • Either • app.use(passport.session()); • passport-http-bearer
15. Client side
16. CORS & Session • Hard work is done on the server • A bit of configuration • Lots of Javascript: need solid tools
17. Tools • Marionnette (http://marionettejs.com) • Component (http://github.com/ component/component) • Jekyll (https://github.com/mojombo/ jekyll)
18. A few thoughts
19. Feels right • More versatile • More isolation: • Simpler to prototype • Easier to maintain and re-use • Easier to secure • Better performances...
20. Questions?