Application of nodejs in epsilon mobile
2 likes868 views
This document discusses using Node.js and Express.js in the backend of an Epsilon mobile application. It outlines how Node.js provides a non-blocking event-driven architecture and how Express.js adds routing, static file serving, authentication, and body parsing middleware capabilities. It also summarizes Epsilon's choices to use Node.js, Express.js, CoffeeScript, Jade, Mocha, Superagent and Should for the backend and Backbone, Jquery, Mocha, Sinon and Require for the frontend. Testing is done with Mocha, Superagent and Should for the backend and Mocha, Require and Sinon for the frontend. The application is integrated with Jenkins for continuous
Application of nodejs in epsilon mobile
- 1. Application of node js in Epsilon Mobile
- 2. Outline • Nodejs • NodeJs deployment • Expressjs • Epsilon’s choices – Back-end – Front-end – Integrate with jenkins
- 3. NodeJs • Event-driven I/O server-side JavaScript environment based on V8 engine.
- 4. Create basic hello world sever • Put the code below into app.js file • Run command node app.js
- 5. Socket io for socket server • Put the code below into app.js file • Run command node app.js
- 6. • Node.js uses an event-driven, non-blocking I/O model -> better than the traditional thread-based server.
- 7. Extensible • Easy to install and easy to use. • There’re already a lot of packages out there.
- 8. Express.js • web application framework for nodejs – Routes – Serve static file vs serve dynamic files – User authentication – Body parser
- 10. Express.js - Serve static files
- 11. User authentication • Use basic authentication
- 12. • Middleware
- 13. Body parser • Decide where to put the upload file • Then, the files’ information will be parsed, the file’s name will be hash.
- 14. Extensible • Body parser is extensible. • Template engine is also extensible.
- 15. Epsilon choices Back-end •nodejs •Expressjs •CoffeeScript, jade •Mocha, superagent, should Front-end •backbone •Jquery •Mocha, sinon, require Others •Jenkins •JSInt (maybe) •JSDuck (maybe)
- 17. Testing for back-end • mocha + superagent + should
- 18. Testing for front-end • mocha + require + sinon – We’re still working on this one.
- 19. spec_runner.js
- 20. test_runner.html
- 21. Integrate with Jenkins for continuous integration
- 22. Our next problems • Trying to setup a Continuous Integration and Continuous Deployment. • Reuse code between server and client. • Generate documents from codes.
Editor's Notes
- #7: Node tells the operating system (through epoll, kqueue, /dev/poll, or select) that it should be notified when a new connection is made, and then it goes to sleep.If someone new connects, then it executes the callback. Each connection is only a small heap allocation.