Node.js an Exectutive View
0 likes341 views
This document provides an overview of Node.js, including what it is, how it works, and why it is useful. Node.js is a runtime environment that allows JavaScript to be used for high-performance, low-latency applications. It uses an event-driven, non-blocking I/O model that makes it efficient even under heavy loads. Node.js is commonly used for backend development, APIs, microservices, and real-time applications due to its fast performance. It also has a large ecosystem of packages and tools that can be used for building applications and development workflows.
Ad
More Related Content
What's hot (20)
Similar to Node.js an Exectutive View (20)
Ad
Recently uploaded (20)
![Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Version](https://cdn.slidesharecdn.com/ss_thumbnails/fashionevolution2-250322112409-f76abaa7-250428124909-b51264ff-250504160528-fc2bb1c5-thumbnail.jpg?width=560&fit=bounds)
Ad
Node.js an Exectutive View
- 1. An Executive View A perspective for business and project management
- 2. Agenda
- 3. WHAT is NOT Node.js isn’t... ● a new language for backend ● a cool new and fashioned tool for frontend ● a Javascript library ● a framework* * Seriously, this is the nearest solution but is not complete
- 4. WHAT is it… A runtime environment designed to use JavaScript in order to develop high-performance and low latency applications. & =
- 5. 80% C++ Libraries 20% JavaScript API image: https://en.wikipedia.org/wiki/Iceberg#/media/File:Iceberg_in_the_Arctic_with_its_underside_exposed.jpg
- 6. WHY is it different It uses an event-driven, non-blocking I/O model that makes it lightweight, efficient and highly-performant even under extreme load, so it… ● Starts really fast. ● Consumes low memory/resources. ● Manages concurrence in an efficient way.
- 7. WHY is it useful Node.js (as many other languages) has lots of tools: - Package Managers (npm, npm search, yarn, bower,...) - Specialized frameworks* (express, restify, hapi, koa, sails) - ORM and DB Connectors (sequelize, mongoose) - Automation Tools (grunt, gulp, npm) - Testing Tools & QA (mocha, plato, istambul) - Multiple Environment managers (nvm) * all the *.js endings were removed from names intentionally, we always relate this suffix with frontend libraries.
- 8. Dev Tools: Java ≈ Node.js ● NPM / YARN ≈ MAVEN Central (public deps downloaded by pom.xml) ● SINOPIA ≈ NEXUS/ARTIFACTORY (private deps downloaded by pom.xml) ● GRUNT / GULP ≈ ANT / MAVEN task/target (build, test, …) ● Express, restify,.. ≈ Spring MVC Framework (helps to build an enterprise app) ● Yeoman ≈ Maven Archetype Plugin (helps to start a project with a seed) ● NVM ≈ update_alternatives (manages multiple SDK versions) uses a package.json file uses a Gruntfile.js script uses a Gulpfile.js script has its own CLI to scaffolding
- 9. HOW is it recommended Node.js (as many other languages) can be used in two main ways: - Local Tooling/Scripting e.g. Grunt, Gulp, Github Atom, Node-WebKit or NPM. - Developing Ad-hoc Network Applications AKA: Server Side Backends
- 10. WHO is using it Data obtained from: nodejs.org/es/foundation & Wikipedia
- 11. WHO is using it Data obtained from: www.modulecounts.com YEAR LIFETIME
- 12. Private Artifact Repository But… I want my own private packages in my projects! ● Use custom code repository (GIT or SVN) and link locally: $git clone git@ip/link my_awesome_corp_module $npm link local/path/o/my_awesome_corp_module ● Use Sinopia and deploy your own server. ● Use a Private SaaS as NPM Enterprise.
- 13. WHERE is it recommended Node.js is powering everything from... ● Enterprise applications ● Robots (means IoT) ● API engines ● Cloud stacks ● Mobile websites ● Local tool development
- 14. WHEN is it recommended ● Backends with non-extensive memory use* ● Low latency apps ● Low-resource environments ● Fast Started Microservices ● Full Stack Web Environments across functionality and roles Yes, these aren’t all the possibilities! * You can still use native C++ libraries or streams to forward data
- 15. But, if it is JavaScript and we still have the usual dev tools... What is new?
- 16. Common problems, misconceptions and pitfalls ● Apache WebServer and NGINX are not necessary anymore* * At least, not to execute and keep running our servers :) JavaNode.js PHP SOURCE CODE SOURCE CODE SOURCE CODE
- 17. Client Side & Server Side ServerClient OUR SERVER APP OUR CLIENT APP DB* * lots of db, e.g. MySQL, MongoDB, Neo4j, Redis...
- 18. A detail from Angular.js, Angular2,... and other SPA source: https://msdn.microsoft.com/en-us/magazine/dn463786.aspx
- 19. Reference Architectures: Two Tier Source: http://blogs.intel.com/api-management/2013/04/04/mobile-friendly-security/two-tier/
- 20. Reference Architectures: Three Tier Source: http://blogs.intel.com/api-management/2013/04/04/mobile-friendly-security/3-tier/
- 21. Reference Architectures: Multi Tier Source: https://www.ibm.com/developerworks/library/wa-aj-multitier/
- 22. Reference Architectures: RESTful Source: https://www.safaribooksonline.com/library/view/restful-java-patterns/9781783287963/
- 23. Any question? Manuel E. de Paz Carmona [email protected]
- 24. Performance References Now, some comparative studies about performance.
- 25. Benchmarking: Apache vs Node.js Node.js Apache PHP Legend Concurrent Users Response Time CPU Consume Sources: http://zgadzaj.com/benchmarking-nodejs-basic-performance-tests-against-apache-php https://code.google.com/p/node-js-vs-apache-php-benchmark/wiki/Tests http://blog.loadimpact.com/2013/02/01/node-js-vs-php-using-load-impact-to-visualize-node-js-efficency/
- 26. Source: http://www.richwandell.com/wordpress/realistic-node-js-vs-apache-php-test/ Benchmarking: Apache vs Node.js
- 27. I/O latency L1: 3 cycles L2: 14 cycles RAM: 250 cycles DISK: 41,000,000 cycles NETWORK: 240,000,000 cycles NGINX also use an event cycle instead a thread by connection like Apache. Benchmarking: Apache vs Nginx Source: http://blog.webfaction.com/2008/12/a-little-holiday-present-10000-reqssec-with-nginx-2/
- 28. References ● Official node.js web and foundation principles: https://nodejs.org/es/foundation ● A slide deck from Node.js people about business data: http://www.slideshare.net/NodejsFoundation/the-enterprise-case-for-nodejs-65523959 ● Yet another node.js introduction http://www.slideshare.net/JamalOGarro/intro-to-nodejs-49431091
- 29. Disclaimer All product names, logos, and brands are property of their respective owners. All company, product and service names used in this slide deck are for identification purposes only. Use of these names, logos, and brands does not imply endorsement. This slide deck is licensed by