Download as KEY, PPTX
Uploaded byAlexandre Morgaut
State of the art - server side JavaScript - web-5 2012
This document provides a history and overview of server-side JavaScript. It discusses the birth of JavaScript in 1995 and key developments through 2011, including the emergence of Node.js and other platforms that enabled JavaScript to be used for server-side applications. Examples of companies using server-side JavaScript in production are provided, such as Demandware, Neolane, MTV, Voxer, and Happy Meeple. Benchmarks of different JavaScript engines and platforms are also referenced.
More Related Content
Similar to State of the art - server side JavaScript - web-5 2012
![Governance, Deployment & Methodologies for Agentic Automation [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day2-251112135038-a386476d-thumbnail.jpg?width=640&height=640&fit=bounds)
State of the art - server side JavaScript - web-5 2012
- 1. STATE OF THEART SERVER-SIDE JAVASCRIPT Web-5 2012-04-05
- 2. PRESENTATION Alexandre Morgaut Web Architect / Community Manager Creator of @NantesJS @amorgaut
- 3.
- 4. BIRTH • 1995 Brendan Eich Mocha > LiveScript > JavaScript (NS2) JavaScript creator • 1996 Microsoft JScript (IE4) NetScape Enterprise Server 2 aka LiveWire/iPlanet • 1997 ECMAScript 1 “DHTML” Windows IIS 3
- 5. The “JavaScript” nameis trademarked by Oracle (via Sun)
- 6. MATURITY • 1998 - HTML/XML DOM, Sun/Mozilla Rhino • 1999 - ECMAScript 3, XMLHttpRequest, HTML 4 • 2000 - ActionScript, Helma Hop • 2001 - JSON, Apple JavaScript OSA • 2002 - JSLint, Mozilla “Phoenix” > Firefox • 2003 - JavaScript Adobe Press, JScript .NET • 2004 - E4X , “Web 2.0”, JSDB • 2005 - Prototype.js, “Ajax” • 2006 - Firebug, jQuery, “Comet”, APE, “HTML5” • 2007 - SitePoint Persevere, Rhino on Rails
- 7. SSJS: THE COMEBACK • 2008 Aptana Jaxer CouchDB Acid Test 3 • 2009 Narwhal & Jack ServerJS > CommonJS Node.js v8cgi, GPSEE ECMAScript 5 • 2010 Helma NG > RingoJS Sun Phobos • 2011 Wakanda CoffeeScript ECMAScript 5.1
- 8. SSJS: THE COMEBACK • 2008 Aptana Jaxer CouchDB Acid Test 3 • 2009 Narwhal & Jack ServerJS > CommonJS Node.js v8cgi, GPSEE ECMAScript 5 • 2010 Helma NG > RingoJS Sun Phobos • 2011 Wakanda CoffeeScript ECMAScript 5.1
- 9. SSJS: THE COMEBACK • 2008 Aptana Jaxer CouchDB Acid Test 3 • 2009 Narwhal & Jack ServerJS > CommonJS Node.js v8cgi, GPSEE ECMAScript 5 • 2010 Helma NG > RingoJS Sun Phobos • 2011 Wakanda CoffeeScript ECMAScript 5.1
- 10. SSJS: THE COMEBACK • 2008 Aptana Jaxer CouchDB Acid Test 3 • 2009 Narwhal & Jack ServerJS > CommonJS Node.js v8cgi, GPSEE ECMAScript 5 • 2010 Helma NG > RingoJS Sun Phobos • 2011 Wakanda CoffeeScript ECMAScript 5.1
- 11. SSJS: THE COMEBACK • 2008 Aptana Jaxer CouchDB Acid Test 3 • 2009 Narwhal & Jack ServerJS > CommonJS Node.js v8cgi, GPSEE ECMAScript 5 • 2010 Helma NG > RingoJS Sun Phobos • 2011 Wakanda CoffeeScript ECMAScript 5.1
- 12.
- 13.
- 14.
- 15. LIBRAIRIES & FRAMEWORKS https://github.com/languages/JavaScript http://javascriptlibraries.com/
- 16. DEVELOPMENT ENVIRONMENTS • Visual Studio • XCode • Eclipse • NetBeans • Wakanda Studio • Cloud9
- 17. DEBUGGERS Client-side •Firebug * • Web Inspector * • Dragonfly Server-Side • Wakanda Debugger * • Cloud9 Debugger * * via standard protocols, some debugger can debug JS code running anywhere (server, desktop, mobile, ...)
- 18. ECMASCRIPT 5 &NEXT • ES5.1 • ES.Next • Mode strict • Typed Array • Object freeze • Modules • Read only properties • Destructuring • Getter / setter • String templates • More native methods • ...
- 19. TOOLS & STANDARDS •JSLint / JSHint / JavaScriptLint • JSON / JSON-Schema / JSONQuery / JSON-RPC • JSDoc / ScriptDoc • JSON View • JSMin / Packer / YUI Compressor / Dojo Shrinksafe • YUI Test / QUnit / Jasmine / Mocha / Selenium • NPM / CPM • RequireJS (r.js) • PhantomJS
- 20.
- 21.
- 22. C+ C + SpiderMonkey webkit JavaScriptCore: JSC 3 JIT Compilers: SquirrelFish Extreme: SFX aka Nitro TraceMonkey, (JIT Compiler inside) JägerMonkey, IonMonkey Jav C+ a + Rhino V8 Interpreted or Compiled execution JIT Compiler: CrankShaft Nashorn? ? Trident: MSHTML Chakra -> Classic JScript, Managed JScript, & JScript.NET C+ ? + Tamarin Carakan JIT Compiler: NanoJIT -> ActionScript / “ECMAScript 4” Previously: Linear A, Linear B, Futhark
- 23. CLIENT-SIDE SpiderMonkey JavaScriptCore Rhino V8 Tamarin Trident / Chakra Carakan / Futhark
- 24. SERVER-SIDE SpiderMonkey JavaScriptCore Rhino V8 Trident / Chakra
- 25. BENCHMARKS and whatthey worth....
- 26. BROWSERS WAR II (MAY 2009) http://www.maximumpc.com/article/features/browser_brouhaha_your_maximum_guide_browsers_today_and_tomorrow?page=0,6
- 27. PERSEVERE & JAVASCRIPTDB (APRIL 2009) http://www.sitepen.com/blog/2009/04/20/javascriptdb-perseveres-new-high-performance-storage-engine/
- 28. NODE VS THINVS NARWHAL (SEPTEMBER 2009) 300 concurrent clients completed requests: thin 36045 node 35668 narwhal 2921 > summary(node300$ttime) Min. 1st Qu. Median Mean 3rd Qu. Max. 12.0 66.0 112.0 239.4 157.0 12200.0 > summary(thin300$ttime) Min. 1st Qu. Median Mean 3rd Qu. Max. 71.0 84.0 87.0 208.7 107.0 23950.0 > summary(narwhal300$ttime) Min. 1st Qu. Median Mean 3rd Qu. Max. 928 2837 2935 2921 3018 8759 http://four.livejournal.com/1019177.html
- 29. RINGOJS VS NODEJS (SEPTEMBER 2010) http://hns.github.com/2010/09/21/benchmark.html
- 30. SUNSPIDER 0.9.1 (AUGUST 2011) 7 8 6 5 4 3 2 1 http://expansive-derivation.ossreleasefeed.com/2011/08/javascript-performance-test-results-with-sunspider/
- 31. EMSCRIPTEN TESTS (OCTOBER 2011) !"#$%&'($)(*+,$-."/ 0 +((',--#+..(./(012&.(+03)4&1*0.%5$12,23 $ ! 677,84#$4#$4#$4#$4#$4#$4#$4#$4#$4#$4 ! 91:13$4#$4#$4#$4#$4#$4#$5#$5#$5#$6#$6 ! ;$1213$4#$4#$4#$5#$5#$5#$5#$5#$5#$7#$8 ! <1#=)223$4#$4#$5#$5#$5#$5#$6#$9#$: ! 6>3$4#$4#$5#$5#$5#$5#$6#$6#$7#$;#$45 ! << ! 91:1;$%&'(3$5#$5#$6#$9#$9#$;$$$$$$$$=">?$12,2#$*",$(&"",">,@ ! << ! ?@(+.*3$4#$6#$:#$6:#$75#$7A#$A4#$:4#$;7#$44B ! A/4@3$7#$:#$;#$54#$5:#$9B#$:A#$;4#$44B#$54A !"#$%&'()* http://syntensity.com/static/jsconf_eu_Emscripten_lo.pdf
- 32. SPIDERMONKEY 1.5 is ~ Firefox 2.0 (and ES-3) 1.7 is ~ Firefox 3.0 1.8 is ~ Firefox 3.6 1.8.5 + JITs is ~ Firefox 4 http://www.page.ca/~wes/SpiderMonkey/Perf/sunspider_history.png
- 33.
- 34. INTEGRATION-ORIENTED • PHP (J2PA, V8JS) - using Rhino like with - Helma, Persevere, Narwhal, RingoJS, • C (GPSEE), Sun Phobos... - Oracle Nashorn? • Objective C (iMonkey), • Ruby (Johnson), - using JScript.NET like with - IronJS, Node.NET • Perl (JE), …
- 35. COMMON JAVASCRIPT • Working Groups: - ECMA TC39 - W3C - WHATWG - CommonJS • Ubiquity beyond ECMAScript • HTML5 specification was also known as: “Web Applications 1.0” http://www.whatwg.org/specs/web-apps/current-work/ • Asynchronous & Synchronous APIs
- 36. ASYNC. EVENT-BASED • Browser’s Event-Loop on the Server • An Event Loop in one single thread • Cooperative («one at a time») with async. callbacks • Node.js (V8), SpiderNode, RhiNodeII, Node.NET
- 37. SINGLE & MULTITHREADING One global context per thread SINGLE MULTI • Low memory usage • Vertical scalability (multi-core) • Potentially handle lot of requests • Thread-safety for concurrent access • Cooperative • Preemptive: Parallel code execution • Shared context • Allow Synchronous APIs • Use mostly one core* • Uses easily all available cores Notes: - an event loop can generate some other threads which could use other cores - multi-thread architectures can run event loops in some of their threads
- 38. DATA-DRIVEN • Document Store • Object Store • Key/value Store • Push engine See also: JSDB, JavaScriptDB
- 39.
- 40. COMMONJS • Modules • Packages • System • Binary • Stream • Unit-Testing • File • Promises • JSGI http://wiki.commonjs.org/wiki/CommonJS
- 41. NODE ASYNC APIS • Buffer • Net • Streams • Events • OS • Timers • File • Process • ... http://nodejs.org/docs/v0.5.5/api/
- 42. W3C / HTML5/ ES.NEXT & OTHER STANDARDS • Console • Typed Arrays • Blob, Blob URL • Web Sockets • DataView • Web Storage, Indexed DB • File / FileSystem • Web Workers • Modules • XHR 2 • Progress Events • DOM, E4X • Structured clones • Messages
- 43. PACKAGES & MODULES •github: CommonJS modules in projects (Persevere, Narwhal, RingoJS, ...) • NPM: Node Package Manager (thousands packages) • CPM: CommonJS Package Manager (new) • PINF: Universal module loader
- 44.
- 45. DEMANDWARE Many shops runon SSJS via Demandware’s commerce platform: London 2012 olympics shop Puma sneaker ... It uses Mozilla Rhino http://jsconf.eu/2010/speaker/server-side_javascript_the_unt.html
- 46. NEOLANE Neolane, a desktopapplication written in C++, is used by clients but also by integrators & partners who need to be able to add their own code JavaScript was chosen because it is a well-known interpreted language The JavaScript engine is SpiderMonkey http://www.neolane.com
- 47. MTV • Current deployments include • SpikeTV.com • Comedy Central Indecision, • MTV Networks will be rolling out MongoDB on many other major sites http://www.mongodb.org/display/DOCS/Production+Deployments
- 48. VOXER Voxer is anext generation application for voice and text messaging “Node.js dramatically outperformed the previous solution we had written in Python” Matt Rainey, RebelVox CTO http://voxer.com/
- 49. HAPPY MEEPLE Using APEproject Synchronization between users Reuse JavaScript code on client and server to have the same intelligence when online and offline http://www.happymeeple.com
- 50. FINANCIAL DATA REPORTS UsingWakanda Deployed on employees iOS, Android, & Blackberry smartphones Provides historical sales and invoices reports in PDF
- 51. THANK YOU Come with us at San Jose, CA on October 26th: @jseverywhere http://jseverywhere.org Alexandre Morgaut - @amorgaut Call to speaker just started!!!
Editor's Notes
- #2 When we started to define the Wakanda project, we did a lot of research and tests before concluding what would be the best language for it on the server and with which engine. We then decided to share with the others what we knew and what we learned. And here come this presentation.\n
- #3 \n
- #4 \n
- #5 Brendan Eich creates JavaScript for NetScape.\n1 year after, he puts it on the server.\nEach time Microsoft followed just one year after.\nThe Server-Side JavaScript is 15 years old.\nBackend developers were not much convinced and mostly choose to ignore it.\n
- #6 \n
- #7 JavaScript long growing maturity.\nMozilla Rhino and Microsoft IIS were the only ones running JavaScript/JScript on the server.\nJavaScript finally had respected standards, development tools, libraries, frameworks, richer APIs\n\n
- #8 Aptana was well respected for its support of JavaScript and JS frameworks in its Studio.\nWhen they tried to launch their Cloud solution with JS on the server via Jaxer, lot of JS experts were enthusiastic. John Resig immediately shared its own experiences on its blog.\nIn 2008, first presentation of Wakanda at The Ajax Experience ;-)\nA group called ServerJS were created from the Mozilla Developper Tools community with Kevin Dangoor.\nIt became more independent and choose to be renamed CommonJS to create standard server-side & client-side JS APIs.\nNode.js proposed an Async Event-Loop model on the server via the Google V8 JS engine. V8 had good reputation, and the concept looked quite revolutionary to JS developers.\nThe Long time running Helma choose to rename Helma NG for a new brand: RingoJS\n
- #9 Aptana was well respected for its support of JavaScript and JS frameworks in its Studio.\nWhen they tried to launch their Cloud solution with JS on the server via Jaxer, lot of JS experts were enthusiastic. John Resig immediately shared its own experiences on its blog.\nIn 2008, first presentation of Wakanda at The Ajax Experience ;-)\nA group called ServerJS were created from the Mozilla Developper Tools community with Kevin Dangoor.\nIt became more independent and choose to be renamed CommonJS to create standard server-side & client-side JS APIs.\nNode.js proposed an Async Event-Loop model on the server via the Google V8 JS engine. V8 had good reputation, and the concept looked quite revolutionary to JS developers.\nThe Long time running Helma choose to rename Helma NG for a new brand: RingoJS\n
- #10 Aptana was well respected for its support of JavaScript and JS frameworks in its Studio.\nWhen they tried to launch their Cloud solution with JS on the server via Jaxer, lot of JS experts were enthusiastic. John Resig immediately shared its own experiences on its blog.\nIn 2008, first presentation of Wakanda at The Ajax Experience ;-)\nA group called ServerJS were created from the Mozilla Developper Tools community with Kevin Dangoor.\nIt became more independent and choose to be renamed CommonJS to create standard server-side & client-side JS APIs.\nNode.js proposed an Async Event-Loop model on the server via the Google V8 JS engine. V8 had good reputation, and the concept looked quite revolutionary to JS developers.\nThe Long time running Helma choose to rename Helma NG for a new brand: RingoJS\n
- #11 Aptana was well respected for its support of JavaScript and JS frameworks in its Studio.\nWhen they tried to launch their Cloud solution with JS on the server via Jaxer, lot of JS experts were enthusiastic. John Resig immediately shared its own experiences on its blog.\nIn 2008, first presentation of Wakanda at The Ajax Experience ;-)\nA group called ServerJS were created from the Mozilla Developper Tools community with Kevin Dangoor.\nIt became more independent and choose to be renamed CommonJS to create standard server-side & client-side JS APIs.\nNode.js proposed an Async Event-Loop model on the server via the Google V8 JS engine. V8 had good reputation, and the concept looked quite revolutionary to JS developers.\nThe Long time running Helma choose to rename Helma NG for a new brand: RingoJS\n
- #12 \n
- #13 \n
- #14 Many User groups, Many Conferences, Many Blogs & books, Large documentation, Language also used by developers from other communities\n
- #15 Most popular language on GitHub\nMany libraries and Frameworks with sometime big Companies behind (Yahoo!, Microsoft, Google, IBM, ...)\n
- #16 \n
- #17 \n
- #18 \n
- #19 \n
- #20 \n
- #21 \n
- #22 Spidermonkey now looks more C++ now but its API are still in C\nComplex Webkit naming\nTrident: Windows only\n
- #23 \n
- #24 SpiderMonkey: Narwhal, CouchDB, MongoDB, JSDB, APE, GPSEE, SpiderNode, ...\nJavaScriptCore: Narwhal, Wakanda\nV8: Narwhal, v8cgi, Akshell, Node.js\nRhino: Narwhal, Helma / RingoJS, AppJet, Persevere, Phobos, RhinodeII, ...\nTrident / Chackra: ASP, WSH, .NET, IronJS, Node.NET\n
- #25 \n
- #26 The growth of WebApps with Ajax Frameworks requires more powerful engines \n-> Browsers War II.\n
- #27 Ici, on compare JS avec d&#x2019;autres technologies : Persevere et son js faisaient plus de req/s que php par exemple\n
- #28 \n
- #29 \n
- #30 The core engines running on the server have finally reach acceptable performances, with quite comparable results.\nThey all actively continue their own performance enhancement.\nECMAScript 5 in strict mode also help to provide better internal optimizations.\n \n
- #31 \n
- #32 Juste en travaillant sur le moteur lui m&#xEA;me a fait d&#x2019;&#xE9;normes gains jusque la 185, puis en ajoutant leur JIT, hop, ils divisent les temps d&#x2019;ex&#xE9;c. par 4.\n\n&#x201C;les autres ont fait pareil dans le m&#xEA;me temps etc...&#x201D; (next slide)\n
- #33 \n
- #34 These solutions were mostly the ones which made JavaScript survive on the server\nAll missing stuff were covered by the environment in which they are running.\nIt&#x2019;s then easy to make it&#x2019;s application platform dependent which often what front-end JavaScript developers want to prevent.\n-> so then came the work on standards for the &#x201C;missing stuff&#x201D; ;-)\n
- #35 &#x201C;JavaScript&#x201D; is available in all modern mobile phones, tablets, Internet box, and even some remote control and TVs.\n- It is quite everywhere, but, back on the server, the JS engines only provide the Core of the language, mostly as defined by ECMAScript with ongoing features. \n- Ajax, Web 2.0, & HTML5 provided a very large & active open source community (first community on Github)\n- At least 4 important Working Groups are doing their best to make it better and better.\n- Common JavaScript oriented implementations want to enhance interoperability between each of them, hopefully more quickly than how it came on client-side.\n
- #36 \n
- #37 \n
- #38 \n
- #39 \n
- #40 \n
- #41 \n
- #42 \n
- #43 \nNPM: Author ?\nCPM: by Kris Zyp\nPINF: by Christoph Dorn\n
- #44 \n
- #45 \n
- #46 \n
- #47 \n
- #48 \n
- #49 \n
- #50 \n
- #51 \n
- #52 \n
- #53 \n
- #54 \n
- #55 \n
- #56 \n
- #57 \n
- #58 \n
- #59 \n
- #60 \n
- #61 \n