"8 1-2 things about serverless (with node.js)" - HolyJS Piter 2017

What is serverless? How does it work? Can you explain it with something as simple as Lego bricks?

This talk will answer that and at least six and a half more questions. It’s main goal is to explain serverless architecture, show you why it’s important, and finally, show you why it works great with Node.js and how to use it.

https://holyjs-piter.ru/en/talks/the-hitchhikers-guide-to-the-serverless-galaxy/

Transcript

1. THINGS ABOUT SERVERLESS WITH NODE.JS
2. #holyjs @slobodan_ CTO AT CLOUD HORIZON AND JS BELGRADE MEETUP ORGANIZER github.com/stojanovic twitter.com/slobodan_ SLOBODAN STOJANOVIĆ
3. #holyjs @slobodan_ ANOTHER SERVERLESS TALK?
4. #holyjs @slobodan_ SOME OF THE QUESTIONS I WILL TRY TO ANSWER TODAY
5. #holyjs @slobodan_ • WHAT IS SERVERLESS? • HOW DOES IT WORK? • WHAT ARE THE SERVERLESS PLATFORMS? • HOW DOES IT WORK WITH NODE.JS? • HOW TO DEBUG SERVERLESS FUNCTION? • WHEN SHOULD YOU USE IT? • IS SERVERLESS SECURE?
6. #holyjs @slobodan_
7. #holyjs @slobodan_ 1. WHAT IS
 SERVERLESS?
8. #holyjs @slobodan_ PLATFORM-AS-A-SERVICE (PaaS)
9. #holyjs @slobodan_ FUNCTION-AS-A-SERVICE (FaaS)
10. #holyjs @slobodan_
11. LET’S TRY TO EXPLAIN IT WITH SOMETHING AS SIMPLE AS LEGO BRICKS
12. #holyjs @slobodan_
13. #holyjs @slobodan_ Imagine Lego 4x4 white piece is a physical server
14. #holyjs @slobodan_ Building and deploying
 monolith app
15. #holyjs @slobodan_ Building and deploying
 monolith app
16. #holyjs @slobodan_ Then people start using it and you need to scale
17. #holyjs @slobodan_ Then people start using it and you need to scale
18. #holyjs @slobodan_ Then people start using it and you need to scale
19. #holyjs @slobodan_ You need to scale everything, but only green and blue parts are really used
20. #holyjs @slobodan_ If one part of the app fails whole system will fail
21. #holyjs @slobodan_ If one part of the app fails whole system will fail
22. #holyjs @slobodan_ If one part of the app fails whole system will fail
23. #holyjs @slobodan_ MICROSERVICES TO THE RESCUE
24. #holyjs @slobodan_ Hello, from our physical server, again! Now it can be in the cloud, it doesn’t matter
25. #holyjs @slobodan_ Now each service should be independent, right?
26. #holyjs @slobodan_ Scaling is easy
27. #holyjs @slobodan_ Scaling is easy
28. #holyjs @slobodan_ And if no one is using some service it’s simple to remove or replace it
29. #holyjs @slobodan_ And if no one is using some service it’s simple to remove or replace it
30. #holyjs @slobodan_ And if some service fails, it doesn’t affect the system
31. #holyjs @slobodan_ And if some service fails, it doesn’t affect the system
32. #holyjs @slobodan_ And if some service fails, it doesn’t affect the system
33. #holyjs @slobodan_ But what if we didn’t scaled it before it fails?
34. #holyjs @slobodan_ ALSO, ARE SERVERS THAT CHEAP?
35. #holyjs @slobodan_ How do we make microservices cheaper?
36. #holyjs @slobodan_ How do we make microservices cheaper?
37. #holyjs @slobodan_ By bundling them together
38. #holyjs @slobodan_ By bundling them together
39. #holyjs @slobodan_ By bundling them together
40. #holyjs @slobodan_ By bundling them together
41. #holyjs @slobodan_ By bundling them together
42. #holyjs @slobodan_ By bundling them together
43. #holyjs @slobodan_ By bundling them together
44. #holyjs @slobodan_ By bundling them together
45. #holyjs @slobodan_ By bundling them together
46. #holyjs @slobodan_ By bundling them together
47. #holyjs @slobodan_ By bundling them together
48. #holyjs @slobodan_ But what if this one fails?
49. #holyjs @slobodan_ IMAGINE WE DON’T NEED 4X4 PIECE ANYMORE?
50. #holyjs @slobodan_ Imagine our microservices without 4x4 white pieces!
51. #holyjs @slobodan_ Than scaling is simply adding more services
52. #holyjs @slobodan_ Than scaling is simply adding more services
53. #holyjs @slobodan_ And, if we don’t need some service…
54. #holyjs @slobodan_ And, if we don’t need some service…
55. #holyjs @slobodan_ And, if we don’t need some service…
56. #holyjs @slobodan_ NOW IMAGINE THAT SCALING IS DONE AUTOMATICALLY
57. #holyjs @slobodan_ If something fails it’s replaced automatically
58. #holyjs @slobodan_ ALSO IMAGINE THAT YOU PAY ONLY FOR THE PARTS THAT YOU ARE USING AT THE MOMENT
59. #holyjs @slobodan_
60. #holyjs @slobodan_ WELL, WE CALL THAT THING SERVERLESS!
61. #holyjs @slobodan_
62. 2. HOW DOES IT WORK?
63. #holyjs @slobodan_ EVENT-DRIVEN
64. #holyjs @slobodan_
65. #holyjs @slobodan_
66. #holyjs @slobodan_
67. #holyjs @slobodan_
68. #holyjs @slobodan_
69. #holyjs @slobodan_
70. #holyjs @slobodan_
71. #holyjs @slobodan_
72. #holyjs @slobodan_
73. #holyjs @slobodan_
74. #holyjs @slobodan_ “LIGHTBULB” == FUNCTION
75. #holyjs @slobodan_ STATELESS
76. #holyjs @slobodan_ SERVERLESS IS LIKE A GOLDEN FISH
77. #holyjs @slobodan_ BUT WHAT ABOUT REAL SYSTEMS?
78. #holyjs @slobodan_
79. #holyjs @slobodan_
80. #holyjs @slobodan_ SERVERLESS APP
81. #holyjs @slobodan_
82. #holyjs @slobodan_
83. #holyjs @slobodan_ • HTTP REQUEST (API) • FILE • NOTIFICATION • MAIL • STREAM • MANY OTHER THINGS WHAT CAN TRIGGER SERVERLESS FUNCTION
84. #holyjs @slobodan_
85. 3. WHAT ARE THE MOST IMPORTANT SERVERLESS PLATFORMS?
86. #holyjs @slobodan_
87. #holyjs @slobodan_
88. #holyjs @slobodan_
89. #holyjs @slobodan_ AWS LAMBDA
90. #holyjs @slobodan_ • $0.20 PER 1 MILLION REQUESTS • FIRST MILLION REQUESTS / MONTH ARE FREE • $0.00001667 FOR EVERT GB-SECOND • FIRST 400.000 GB-SECONDS / MONTH ARE FREE
91. #holyjs @slobodan_ • TIMEOUT UP TO 300 SECONDS • 128MB TO 1.5GB OF MEMORY • 500MB OF NON-PERSISTENT STORAGE (/TMP) • DEFAULT CONCURRENT EXECUTION LIMIT: 1000
92. #holyjs @slobodan_ WHAT PROGRAMMING LANGUAGE YOU NEED TO USE FOR SERVERLESS?
93. #holyjs @slobodan_ • NODE.JS • PYTHON • JAVA • C# • SHELL SCRIPTS • ANY EXECUTABLE AWS LAMBDA
94. #holyjs @slobodan_ • NODE.JS • C# • F# • PYHON • PHP • SHELL SCRIPTS • ANY EXECUTABLE AZURE FUNCTIONS
95. #holyjs @slobodan_ GOOGLE CODE FUNCTIONS JUST NODE.JS AT THE MOMENT
96. #holyjs @slobodan_
97. 4. WHY IS IT IMPORTANT?
98. #holyjs @slobodan_ MINIMAL MAINTENANCE
99. #holyjs @slobodan_ FINANCIAL INCENTIVE https://gojko.net/2016/08/27/serverless.html
100. #holyjs @slobodan_ TRUE MICROSERVICES
101. #holyjs @slobodan_ AUTO SCALING AND FAILOVER
102. #holyjs @slobodan_ FOCUS ON BUSINESS LOGIC, NOT CONFIGURATION
103. #holyjs @slobodan_
104. 5. HOW DOES IT WORK WITH NODE.JS?
105. #holyjs @slobodan_
106. #holyjs @slobodan_ • GOOD STARTUP PERFORMANCE • SMALL MODULES • PERFORMANCE WITH LOW CPU AND MEMORY • SINGLE THREAD • EASY TO LEARN PROS
107. #holyjs @slobodan_ • ASYNC • MADE FOR SCALABILITY • NODE_MODULES SIZE • EASY TO FUCKUP CONS
108. #holyjs @slobodan_ ‘use strict’ console.log(‘Loading event’) exports.handler = (event, context, callback) => { console.log(‘“Hello”: ”World”’) callback(null, {“Hello”: ”World”}) } hello-world.js
109. #holyjs @slobodan_ • CREATE LAMBDA FUNCTION • UPLOAD ZIP FILE • CREATE API GATEWAY • SET TRIGGER • SET PERMISSIONS • ~11 MINS READ: http://amzn.to/2kciIEt HOW TO DEPLOY IT TO AWS
110. #holyjs @slobodan_ • SERVERLESS FRAMEWORK • CLAUDIA.JS • APEX FRAMEWORKS
111. #holyjs @slobodan_ CLAUDIAJS.COM > 69.000 DOWNLOADS
112. #holyjs @slobodan_
113. #holyjs @slobodan_ • DEPLOY AND UPDATE WITH SINGLE COMMAND • USE STANDARD NPM MODULES • NO BOILERPLATE, JUST FOCUS ON YOUR WORK • MANAGE MULTIPLE VERSIONS EASILY • GET STARTED QUICKLY, FLAT LEARNING CURVE MAIN CHARACTERISTICS
114. #holyjs @slobodan_ FLAT LEARNING CURVE HOW FAST CAN WE START?
115. #holyjs @slobodan_
116. #holyjs @slobodan_ • npm i claudia -g • SET UP AWS CREDENTIALS (ONE TIME) • mkdir claudia-api && cd $_ • npm init -f • npm i claudia-api-builder -S prepare
117. #holyjs @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const jokes = require(‘./jokes.json’) api.get(‘/‘, () => jokes) module.exports = api api.js
118. #holyjs @slobodan_ claudia create \ --region eu-central-1 \ --api-module api DEPLOY
119. #holyjs @slobodan_ { "lambda": { "role": "chuck-norris-api-executor", "name": "chuck-norris-api", "region": "eu-central-1" }, "api": { "id": "d1weoszyg7", "module": "api", "url": "https://9fg0wqctc4.execute-api.eu- 
 central-1.amazonaws.com/latest" } } RESULT
120. #holyjs @slobodan_ bit.ly/holyjs-chuck-api
121. #holyjs @slobodan_ bit.ly/holyjs-chuck-api
122. #holyjs @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const jokes = require(‘./jokes.json’) api.get(‘/‘, () => jokes) api.get(‘/{id}’, req => jokes.filter(joke => joke.id === req.pathParams.id ))) api.get(‘/random‘, () => jokes[ Math.floor(Math.random() * jokes.length) ]) module.exports = api api.js
123. #holyjs @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const jokes = require(‘./jokes.json’) api.get(‘/‘, () => jokes) api.get(‘/{id}’, req => jokes.filter(joke => joke.id === req.pathParams.id ))) api.get(‘/random‘, () => jokes[ Math.floor(Math.random() * jokes.length) ]) module.exports = api api.js
124. #holyjs @slobodan_ claudia update UPDATE
125. #holyjs @slobodan_ /random bit.ly/holyjs-chuck-api
126. #holyjs @slobodan_ /42 bit.ly/holyjs-chuck-api
127. #holyjs @slobodan_ // … api.get(‘/{id}’, req => { console.log(req.pathParams) return jokes.filter(joke => joke.id === req.pathParams.id ) }) // … api.js
128. #holyjs @slobodan_
129. 6. HOW TO DEBUG SERVERLESS FUNCTION
130. #holyjs @slobodan_ WHERE CAN YOU SEE
 CONSOLE.LOG?
131. #holyjs @slobodan_ CLOUD WATCH
132. #holyjs @slobodan_ MONITORING SERVICE FOR AWS CLOUD RESOURCES AND THE APPS YOU RUN ON AWS
133. #holyjs @slobodan_ YOU CAN USE IT VIA WEB CONSOLE, AWS CLI, ETC.
134. #holyjs @slobodan_ aws logs get-log-events \ --log-group-name /aws/lambda/chuck-norris-api \ --log-stream-name 2017/05/31/…\ --output json
135. #holyjs @slobodan_ { "nextForwardToken": “f/33366982080235359…”, "events": [ { … }, { "ingestionTime": 1496227223886, "timestamp": 1496227223884, "message": “2017-05-31T10:40:23.805Z\t8d2-45ed…\t{ id: '42' }\n" }, { … }, { … } ], "nextBackwardToken": “b/333669820769…” } OUTPUT
136. #holyjs @slobodan_ { "nextForwardToken": “f/33366982080235359…”, "events": [ { … }, { "ingestionTime": 1496227223886, "timestamp": 1496227223884, "message": “2017-05-31T10:40:23.805Z\t8d2-45ed…\t{ id: '42' }\n" }, { … }, { … } ], "nextBackwardToken": “b/333669820769…” } OUTPUT
137. #holyjs @slobodan_
138. #holyjs @slobodan_ // … api.get(‘/{id}’, req => jokes.filter(joke => joke.id == req.pathParams.id )[0]) // … api.js
139. #holyjs @slobodan_ /42 bit.ly/holyjs-chuck-api
140. #holyjs @slobodan_ DEBUGGING IS NOT FUN. HOW CAN WE DO LESS DEBUGGING?
141. #holyjs @slobodan_ BY WRITING TESTS
142. #holyjs @slobodan_ BUT HOW DO YOU TEST SERVERLESS FUNCTIONS?
143. #holyjs @slobodan_ AS ANY OTHER NODE.JS LIBRARY !
144. #holyjs @slobodan_ EXAMPLE? CLAUDIA-BOT-BUILDER SPECS
145. #holyjs @slobodan_ AWS X RAY
146. #holyjs @slobodan_
147. #holyjs @slobodan_
148. #holyjs @slobodan_ EASIEST WAY TO LEARN SERVERLESS? GO AND PLAY WITH IT!
149. #holyjs @slobodan_ FUNNIEST WAY TO LEARN SERVERLESS? "
150. #holyjs @slobodan_ SERVERLESS.CAMP
151. #holyjs @slobodan_
152. 7. WHEN SHOULD I USE SERVERLESS?
153. #holyjs @slobodan_ LET’S START WITH WHEN YOU SHOULD NOT USE SERVERLESS?
154. #holyjs @slobodan_ • REAL-TIME APPS WITH WEB SOCKETS • LOW-LATENCY APPS • WHEN YOU NEED CUSTOM SERVER CONFIG • WHEN YOU NEED COMPLIANCE • LONG RUNNING TASKS • COMPEX COMPUTING • WHEN YOU NEED TO PROVIDE SLA
155. #holyjs @slobodan_ OK, BUT WHAT IS IT GOOD FOR?
156. #holyjs @slobodan_ • WEB API • BACKEND FOR THE SINGLE PAGE APP • CHATBOTS • QUICK PROTOTYPES THAT CAN EVOLVE TO 
 A REAL SOLUTIONS • PROCESSING FILES OR ANY KIND OF DATA • IoT • MANY, MANY OTHER THINGS
157. #holyjs @slobodan_ HOW CAN YOU START USING IT TODAY?
158. #holyjs @slobodan_ SIDE PROJECT OR SOMETHING SMALL AWS LAMBDA + AWS ECOSYSTEM
159. #holyjs @slobodan_ MOVE SOME NON-ESSENTIAL FEATURE TO SERVERLESS EXISTING APP + FEATURE IN AWS LAMBDA
160. #holyjs @slobodan_
161. 8. IS SERVERLESS SECURE?
162. #holyjs @slobodan_
163. #holyjs @slobodan_ • SERVER “EXISTS” FOR FEW HUNDREDS OF MS • READ-ONLY, EXCEPT /TMP • NO DEDICATED SERVER • SANDBOX / CONTAINERS • NO CONFIGURATION • AUTO SCALING • AWS ECOSYSTEM AWS LAMBDA SECURITY
164. #holyjs @slobodan_ • BAD CODE • BAD PERMISSIONS • 3RD PARTY LIBRARIES • PROBLEMS WITH OTHER BUILDING BLOCKS,
 SUCH AS SQL INJECTION • KEYS AND SECRETS PROBLEMS
165. #holyjs @slobodan_ SO, IS IT SECURE? IT DEPENDS ON YOU
166. #holyjs @slobodan_ THERE ARE VULNERABLE PARTS, BUT IT’S A BETTER SET OF PROBLEMS TO DEAL WITH
167. #holyjs @slobodan_
168. 8 1/2. WAIT, WHAT ABOUT THE NAME?
169. #holyjs @slobodan_ LESS IS MORE
170. #holyjs @slobodan_ LESS IS MORE SERVER SERVERS
171. #holyjs @slobodan_
172. #holyjs @slobodan_ 2012
173. #holyjs @slobodan_ “WHY THE FUTURE OF SOFTWARE AND APPS IS SERVERLESS” BY KEN FROMM
174. #holyjs @slobodan_ 2014
175. #holyjs @slobodan_ AWS LAMBDA
176. #holyjs @slobodan_ 2015
177. #holyjs @slobodan_ API GATEWAY
178. #holyjs @slobodan_ “SERVERS ARE DEAD..” BY ANT STANLEY
179. #holyjs @slobodan_ “SERVERS ARE DEAD..” BY ANT STANLEY
180. #holyjs @slobodan_ JAWS BECOMES SERVERLESS FRAMEWORK
181. #holyjs @slobodan_ 2016
182. #holyjs @slobodan_ “SERVERLESS” IS JUST A NAME. WE COULD HAVE CALLED IT “JEFF” PAUL JOHNSTON
183. #holyjs @slobodan_ “IT IS SERVERLESS THE SAME WAY WiFi IS WIRELESS” GOJKO ADŽIĆ
184. #holyjs @slobodan_ NOW
185. #holyjs @slobodan_ SERVERLESS IS EVERYWHERE
186. #holyjs @slobodan_
187. #holyjs @slobodan_ • SERVERLESS IS FULLY MANAGED FaaS THAT
 HELPS YOU TO FOCUS ON YOUR BUSINESS LOGIC • EVENT-DRIVEN - MANY THINGS CAN TRIGGER FUNCTION • AUTO SCALING AND AUTO FAILOVER • IT WORKS NICE WITH NODE.JS • 3 MAJOR NODE.JS FRAMEWORKS • IT’S TRICKY TO DEBUG, SO WRITE TESTS • GO AND TRY IT, IT’S EASY TO LEARN # SUMMARY
188. #holyjs @slobodan_ ALSO, SERVERS STILL EXIST BUT THEY ARE NOT YOUR PROBLEM
189. #holyjs @slobodan_ ALSO, SERVERS STILL EXIST BUT THEY ARE NOT YOUR PROBLEM
190. #holyjs @slobodan_
191. THAT'S IT.
 THANKS!
192. КОНЕЦ
193. QUESTIONS? @slobodan_ bit.ly/holyjs-serverless #holyjs