Downloaded 46 times
Uploaded byBrainhub
Why and How You Should Move from PHP to Node.js
The document discusses the advantages of moving from PHP to Node.js, emphasizing its asynchronous nature, scalability, and active development. It highlights the versatility of JavaScript and Node.js, mentioning tools and frameworks that facilitate development and integration of both front-end and back-end systems. The author encourages learning resources and experimentation to adapt to this modern web technology.
More Related Content
Similar to Why and How You Should Move from PHP to Node.js
Why and How You Should Move from PHP to Node.js
- 1. Why & HowYou Should Move from PHP to Node.js
- 2. Piotr Kowalski CTO@Brainhub
- 4.
- 5.
- 6. Some thoughts aboutPHP (my personal selection) ● Got used to HTTP (rather request processing than application) ● Many PHPisms, inconsise API (past days) ● Many libraries from many sources ● Tremendous community ● Pretty adult
- 7.
- 8. Brief history ● Writtenin 10 (!) days of May 1995 (name: Mocha) ● Deployed in Netscape Navigator 2.0 in December same year ● Standarisation process since 1996 - ECMAScript ● Browser wars ● Many descendants - JScript, ActionScript and so on… ● NOT DEAD!
- 9. What is JavaScriptnot a.k.a. popular myths ● Given a web page, add me some animation magic ● Do me some AJAX magic ● Some stuff that cannot be kept tidy ● Works different on every browser ● You write $ then some CSSish selector, then you do stuff ● It’s only for the Web ● Some people call it node, but I have no idea why ● There are no classes, it’s not real OO language ● Everyone knows JavaScript, so why bother?
- 10. What about node.js? ●A V8 JavaScript engine ● Multiplatform ● Versatile ● Fast (in a runtime) ● Actively developed (current version 7.0.0) ● ...some more
- 12. Asynchronous event loopwith non-blocking I/O
- 14. Asynchronous event loopwith non-blocking I/O
- 15. Node Package Manager ●Packages count: 344694 (as for today) ● Actively developed
- 16. Realtime application >processing requests ● A web server works as a continuous process, doesn’t restart everytime a new HTTP request is coming ● Can be stateless, but don’t have to be so ● We can get beyond the HTTP (WebSockets, HTTP2, SPDY and so on) ● Does a web server should only create response?
- 17. Fast prototyping andpivoting
- 18. Scalability ● Horizontally scalable ●Since it runs a process it can be easily ran on multiple machines and load balanced ● Thin runtime environment
- 19. One can builda desktop app ● Electron ● NW.js ● APPjs
- 20.
- 21. Isomorphic front- andbackend ● Common codebase both for the backend and the frontend ● No more redundant code!
- 22. WebSockets is afuture of the Web (IMO)
- 23. Node native extensions Onecan write native modules/extensions to node.js (C/C++/Objective-C)
- 24. One can runit even on a coffee machine
- 26.
- 27. How should Istart?
- 29.
- 30.
- 31.
- 32. Subscribe to someblogs/feeds ● http://www.echojs.com/ ● https://davidwalsh.name/ ● http://jstherightway.org/ ● https://www.sitepoint.com/ ● https://medium.com/@dan_abramov ● http://javascriptweekly.com
- 33.
- 34. Play around andbring your ideas to life!
- 35. Come to thenext #devduck!