nodeJS, claypool, APE, map reduce en nosql, yql... Le javascript server side est un sujet d'actualité, une tendance de fond est en train d'émerger. Et la mise en avant des outils dans la communauté progresse rapidement. La promesse d'un seul langage sur le client et le serveur d'une application web est très attirante alors que HTML5, les websockets, les webworker, les local storage sont en train de se faire une place dans le futur du web. Cette conférence a pour but de vous permettre de mieux appréhender cet écosystème à travers son historique, l'exposé des standards émergeant, des avantages et défauts des différentes solutions proposées et en présentant les briques communes. Quels projets pouvez vous entreprendre sur ces technologies ? Est-ce possible à intégrer en production ? L'administration et l'intégration de ces outils au SI d'une entreprise est il possible ? Ces technologies vont elles s'implanter ou rester des expérimentations de techniciens sous stéroïdes ?

1. The javascript server side : how to start ? Confoo 2011 – Quentin ADAM @waxzce

2. Who I am ? Quentin ADAM @waxzce on twitter or github CEO atClever Cloud

3. Javascript Where ? When ? Why ?

4. What are wedoingwithJavascripttoday ? Application server Database RIA Browser

6. History At the begining, Brendan Eich, created Live Script (1995) at Netscape for server usage. It is the Netscape Server procuct. The Javascript name is a maketing change by Sun and Netscape.

7. The polyglotte situation Client Server Php Java Perl Ruby Scala Groovy ….

8. About polyglots and langages

9. Share some code between client and server Unity of tools and environement Agile Have the same Model No « translations » of objects

10. Some Strength for modern and social apps Event driven NoSQL & Json Use some datas with unknow format

11. One lang, someengines

12. A standard (or not) & Many implementations (or not) Engine = Tools making compilation to bytecode + conversion to bynary instruction = virtual machine javascript {trace, spider, jäger…}Monkey V8 M$ applenitro Rhino

13. A standard (or not) & Many implementations (or not) {trace, spider, jäger…}Monkey V8 M$ applenitro Rhino Narcissus (zaphod)

14. engine JS ≠ Browser

15. No DOM No jquery No mootools No dojo… Except server versions

16. A web server RESTfull

17. One of bigest change of ssjs :event driven web response, async 0_0 Don’t panic, some schema next slide

18. without

19. With

20. Whatweneed ?

21. Sometools Names

22. Ajax Push Engine Design for real time web Stable and strongproject Mootoolsframework Mysql support http://www.ape-project.org/

23. How to ?

24. Mongo DB Document orienteddatabase Store data as Bjson Workwith a lot of platform

25. Mapreduce A new way for geting data working on a lot of noSQL DB

26. Node.js : The Star

28. How to ? Entry point file

29. frameworksnode Sinatra like : express Rails like : Geddy !! -> tools are not ready Ruby & node.js

30. CommonJS Unity for JS platform of usual API require() http://www.commonjs.org/

31. How to begin ? And be happy with new tools

32. Create a githubaccount All ssJsprojects are on github Frameworks, modstoo Examples You needitanyway

33. Have a real OS You need real command line You need compilation tools You needitanyway UNIX Tips : use ZSH withyour git

34. Test node.jswith cloud9 Online IDE for node.js Nothing to install Workwithgithub

35. Make an open table for YQL SQL likelang for web API Workingwithssjs Rhino backend You needonly a server storingyour table

36. Play withmongoDB or couchDB Easy to install Usefull Simple to use withssjsplatform

37. Install APEtest it

38. Include Rhino in your java projects Include in the JDK Usefull for scripting Usefullworking on unsafe data Addevent layer withAtmoshpere or Akka

39. Writesomekickassapp

40. The checklist What I need ? Can I split the application ? What about mysysadminskills ? Is the appcritical ? Think about yourproblemswiththeses solutions

41. Thx