Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

From Java To Node.js

5,140 views

Published on

Delivered at Shine Technologies Developers Meeting - August 2011.

Published in: Technology, Business
  • Be the first to comment

From Java To Node.js

  1. 1. From Java To Node.jsCliffano Subagio (@cliffano)
  2. 2. Bleeding Edge
  3. 3. Why use Node.js?
  4. 4. Multi Threaded Single Threaded Blocking Non-blocking Java JavaScript
  5. 5. Somebody gonna get a hurt
  6. 6. Memory usage300Mb270Mb240Mb210Mb Single Threaded Multi Threaded180Mb150Mb120Mb 90Mb 60Mb 30Mb 0Mb 1 request 10 requests
  7. 7. Blocking Non-blockingcafes = db.getCafes(); callback = func (cafes) {print(cafes); print(cafes); } db.getCafes(callback);
  8. 8. Seriously Fast!
  9. 9. Java JavaScript
  10. 10. I’m feeling productive!
  11. 11. Best Practice
  12. 12. SoIt works. It has obvious benefits. Definitely worth considering.
  13. 13. Questions?
  14. 14. CreditsFlickr Creative Commons http://www.flickr.com/photos/tomsaint/2704534525/ by Rennett Stowe http://www.flickr.com/photos/jcorduroy/4314537558/ by Jay Malone http://www.flickr.com/photos/jamescridland/1305153543/ by James Cridland http://www.flickr.com/photos/ashleyyyray/3630230385/ by Ashley Maceli http://www.flickr.com/photos/viernest/3380560365/ by Ernest http://www.flickr.com/photos/rogerimp/3181052163/ by Roger Braunstein http://www.flickr.com/photos/sookie/2491485992/ by Sookie http://www.flickr.com/photos/richardgunn/1795691766/ by Richard

×