Node.js Crash Course - Indy.Code() 2018

Node.js is a compelling platform that is quickly spreading from startups to the enterprise. Node.js strategically unites developers of all backgrounds through the common language of JavaScript. Why should you learn Node.js and where do you start? You will come away from this talk with the evidence to support Node.js, and tools you need to be productive. We will walk through a typical workflow of creating and debugging a web application. You will learn how easy it is to deploy, including Microsoft Azure. We'll also look at popular frameworks and modules, and other learning resources to give you the best start.

Transcript

2. JavaScript… …has won the Web. Scott Hanselman
3. Any application that can be written in JavaScript… …will eventually be written in JavaScript (search for “jslinux”) Atwood’s Law:
4. JavaScript… …is tragically important. Douglas Crockford
11. Up Ahead • Why Node.js? • Crash course • Tools and frameworks • Integration strategies
19. ES 2016 (ES6) Support https://kangax.github.io/compat-table/es6/
20. What’s my story? • ASP.NET MVC, C# • SQL Server + NHibernate • JavaScript + JQuery
23. What’s my story? • JavaScript • Recruiting • Productive, less friction – Testing – Microservices – RabbitMQ, redis – Cross-platform
25. Why Node.js? • Rapid innovation & delivery • Developer happiness • Attract & retain talent • Performance “Why Node.js is Becoming the Go-To Technology in the Enterprise” – nearform.com
26. Why Node.js? productivity satisfaction performance lower costs Improved results year-over-year 2017 Node.js Foundation User Survey, Executive Summary
27. Node.js exemplifies… • Start with the simplest solution that works • Do one thing, and do it well
28. • Backend API for SPAs, Mobile apps, etc. • “Serverless” computing • Real-time, streaming • WebSockets, push notifications • Chat, IM, social media • DevOps • Microservices Node.js Use Cases
29. Node.js Use Cases • Backend API for SPAs, Mobile apps, etc. • “Serverless” computing • Real-time, streaming • WebSockets, push notifications • Chat, IM, social media • DevOps • Microservices
30. More than just backend • Create Automation Scripts • Internet of Things • Create CLI tools using nexe • Create Desktop Apps
31. Atom Slack Visual Studio Code
32. Fandango • dramatically shorter development cycles • micro-services architecture • flexibility in deployment • easily scalable infrastructure “Fandango Goes Live with Node.js” – nearform.com
33. • 2x faster development with fewer developers • 33% fewer lines of code • 40% fewer files • 2x improvement requests/sec • 35% decrease in avg response time
34. • Black Friday, 2013 • Mobile platform • 200,000,000+ users • 10 CPU cores, 28 GB RAM • < 1% CPU utilization • Deployed updates
35. Who else is using Node.js? • NASA • Netflix • Amazon • Medium • GE • Wordpress • CapitalOne • eBay • Target • Airbnb • Samsung • GoPro
36. DevOps • Small footprint • Cross-platform • Event-driven • OSS tools • Containers
37. “What is Node.js used for: The 2015 Node.js Overview Report” – blog.risingstack.com
38. Installing Node.js https://nodejs.org
39. Installing Node.js Mac or Linux? Use nvm! https://github.com/creationix/nvm Windows? Use Chocolatey! https://chocolatey.org/ C:\> choco install nodejs.install > nvm install 8
40. Installing Node.js > node –v v8.11.1 > npm –v 5.6.0
42. module-usage-example.js
43. module-usage-example.js
44. module-usage-example.js
45. module-usage-example.js
46. module-usage-example.js
47. callback-example-1.js
48. callback-example-1.js
49. callback-example-1.js
50. callback-example-2.js
51. callback-example-2.js
52. callback-example-2.js
53. callback-example-2.js
54. callback-example-3.js
55. callback-example-3.js
56. callback-example-3.js
57. callback-example-3.js
58. temperature.js
59. temperature.js
60. temperature.js
61. temperature.js
62. temperature.js temp-example.js
63. temperature.js temp-example.js
64. temperature.js temp-example.js
65. temperature.js temp-example.js
66. temperature.js temp-example.js
67. config.js
68. config.js
69. config.js
70. config.js
71. config.js
72. config.js
73. config.js
74. config.js cfg-example.js
75. config.js cfg-example.js
76. config.js cfg-example.js
77. config.js cfg-example.js
78. config.js cfg-example.js
79. config.js cfg-example.js app.json
80. sql-example.js
81. sql-example.js
82. sql-example.js
83. sql-example.js
84. sql-example.js
85. sql-example2.js
86. sql-example2.js
87. sql-example2.js
88. Deploying • Windows – iisnode for web apps – winser for services • Linux – forever • Docker
89. Hosting Node.js on Azure • New Node JS Empty Site • Connect to repository • reverentgeek.com/hosting-node-js-on-microsoft-azure/
90. Recommended toolbox Package What it do, yo lodash JavaScript utilities async async/parallel execution request, axios, or wreck http clients socket.io sockets, real-time jest, mocha, or lab test frameworks testdouble spies, stubs, mocks
91. Node frameworks MVC • Express • hapi • koa • Meteor • Sails API • Restify • LoopBack nodeframework.com
92. • Run .NET in-process • …including F#, ADO.NET, Python, and Powershell • Execute inline code, files, or assemblies • Alternative to writing native modules in C • .NET 4.5 or Mono 3.1
93. What can Edge.js do? • Leverage existing .NET investment • TFS, SharePoint, Exchange, etc. • Active Directory • Hardware (e.g. camera, microphone, printer, win32) • Video encoding, or other CPU- intensive work • Powershell
94. Node.js Integration Strategies • Node.js as proxy or nginx • request module to call APIs • Messaging (e.g. RabbitMQ, ZeroMQ Azure Service Bus) • Edge.js for .NET
96. http://bit.ly/node-crash-course