State of the art: Server-Side JavaScript (ParisJS)
10 likes9,285 views
The document reviews the evolution and current state of server-side JavaScript, discussing its history from 1995 through various frameworks and solutions, highlighting significant milestones such as the introduction of Node.js and ECMAScript 5. It compares performance and usage of different JavaScript engines and solutions like Rhino, V8, and CouchDB, and explores asynchronous event-based programming models. The document also covers package management systems such as npm and emphasizes the growing ecosystem around server-side JavaScript.
State of the art: Server-Side JavaScript (ParisJS)
- 1. State of the Art Server-Side JavaScript #10 @amorgaut 4d.com @thibarg 2011-08-31
- 2. Notes These slides are part of a 15min version of the talk for ParisJS a more recent version has been presented at WebWorkersCamp IV during Open World Forum http://www.slideshare.net/alexandre_morgaut/state-of-the-art-server-side-java-script-webworkerscamp-9406069
- 3. History
- 4. Birth 1995 LiveScript/JavaScript 1996 Microsoft JScript (IE4) NetScape Enterprise Server 2 aka LiveWire/iPlanet 1997 ECMAScript 1 “DHTML” Windows IIS 3
- 5. Maturity 1998 - DOM, Mozilla Rhino 1999 - ES3, XMLHttpRequest, HTML 4 2000 - ActionScript, Helma Hop 2001 - JSON, Apple JavaScript OSA 2002 - JSLint 2003 - JavaScript Adobe Press 2004 - E4X , “Web 2.0” 2005 - Prototype, “Ajax” 2006 - Firebug, jQuery, “Comet”, “HTML5” 2007 - SitePoint Persevere, Rhino on Rails
- 6. SSJS: The comeback 2008 Aptana Jaxer CouchDB 2009 Narwhal & Jack ServerJS/CommonJS Node.JS ECMAScript 5 2010 Helma NG -> RingoJS Sun Phobos 2011 Wakanda
- 7. SSJS: The comeback 2008 Aptana Jaxer CouchDB 2009 Narwhal & Jack ServerJS/CommonJS Node.JS ECMAScript 5 2010 Helma NG -> RingoJS Sun Phobos 2011 Wakanda
- 8. SSJS: The comeback 2008 Aptana Jaxer CouchDB 2009 Narwhal & Jack ServerJS/CommonJS Node.JS ECMAScript 5 2010 Helma NG -> RingoJS Sun Phobos 2011 Wakanda
- 9. SSJS: The comeback 2008 Aptana Jaxer CouchDB 2009 Narwhal & Jack ServerJS/CommonJS Node.JS ECMAScript 5 2010 Helma NG -> RingoJS Sun Phobos 2011 Wakanda
- 11. Engines
- 12. Engines SpiderMonkey webkit JavaScriptCore: JSC TraceMonkey (JIT) SquirrelFish Extreme: SFX (JIT) JägerMonkey (JIT) IonMonkey (JIT) Nitro Rhino V8 Trident Chakra Carakan Tamarin Futhark
- 13. Engines C/ C/ C+ C+ + + SpiderMonkey webkit JavaScriptCore: JSC Narwhal Narwhal CouchDB, MongoDB Wakanda Spidernode ... ... Sp ide C/ rM C+ o nk + Rhino V8 ey in Ja va Narwhal Narwhal RingoJS Akshell Persevere Node.js ... C/ ... C+ Trident / Chakra + ASP / .NET
- 14. Benchmarks?
- 15. Persevere JavaScriptDB (April 2009) http://www.sitepen.com/blog/2009/04/20/javascriptdb-perseveres-new-high-performance-storage-engine/
- 16. Node vs Thin vs 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
- 17. RingoJS vs NodeJS (September 2010) http://hns.github.com/2010/09/21/benchmark.html
- 18. 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/
- 19. Main Concepts
- 20. Integration-Oriented Rhino SpiderMonkey in Java Interaction with Java (APIs and objects) Helma, Persevere, Narwhal*, RingoJS, Sun Phobos... JScript .Net Chakra (C++) Interaction with Windows APIs
- 21. Async. Event-based One single thread Cooperative («one at a time») with async. callbacks nodejs (V8)
- 22. Async. Event-based One single thread Cooperative («one at a time») with async. callbacks nodejs (V8) Cons Pros Vulnerable to synchronous Can handle a lot of operations requests Share failure Low memory usage Doesn’t use other cores Uses only one core Hard to debug and maintain
- 23. Thread-based One thread per context Preemptive: Parallel code execution About all others
- 24. Thread-based One thread per context Preemptive: Parallel code execution About all others Cons Pros Memory/CPU limits Vertical scalability (cloud) Race conditions, deadlocks, ... Thread-safety for concurrent (internal, C++) access Uses all available cores Uses all available cores
- 25. Database-driven CouchDB, MongoDB (SpiderMonkey): Document Store Wakanda (JavaScriptCore) Object Store
- 26. APIs
- 27. CommonJS Modules Binary Packages File Promises JSGI System Stream Unit-Testing http://wiki.commonjs.org/wiki/CommonJS
- 28. Node.js async APIs Buffer Streams Events Timers File ... Net OS Process http://nodejs.org/docs/v0.5.5/api/
- 29. W3C / HTML5 & other standards Console Structured clones Blob, Blob URL* Typed Arrays* DataView* Web Sockets File / FileSystem Web Storage Modules* Web Workers Progress Events XHR 2
- 30. Packages & Modules github lot of commonjs modules in several repositories (Persevere, Narwhal, RingoJS, ...) NPM: Node Package Manager 3600+ packages CPM: CommonJS Package Manager (new) http://wiki.commonjs.org/wiki/CommonJS
- 31. State of the Art Server-Side JavaScript The End See us at Wakanday aka JS.everywhere(Boston, October, 15) @amorgaut 4d.com @thibarg wakanday.org @wakandasoft @wakanday
Editor's Notes
- #4: Brendan Eich creates JavaScript for NetScape 1 year after, he puts it on the server Each time Microsoft followed just one year after
- #5: JavaScript long growing maturity
- #6: Server-Side JavaScript: the come back
- #11: Maturité de l’environement (Tools, Standards, libraries) mais aussi montée des performances “ The JavaScript Performance Race”
- #16: Maturité de l’environement (Tools, Standards, libraries) mais aussi montée des performances “ The JavaScript Performance Race”