8 ½ things about serverless - FDConf 2017

https://fdconf.by/en/8-1-2-things-about-serverless-2/

Transcript

1. THINGS ABOUT SERVERLESS WITH NODE.JS
2. THINGS ABOUT SERVERLESS WITH NODE.JS
3. #FDConf @slobodan_ CTO AT CLOUD HORIZON AND JS BELGRADE MEETUP ORGANIZER github.com/stojanovic twitter.com/slobodan_ SLOBODAN STOJANOVIĆ
4. #FDConf @slobodan_ ANOTHER SERVERLESS TALK?
5. #FDConf @slobodan_ SOME OF THE QUESTIONS I WILL TRY TO ANSWER TODAY
6. #FDConf @slobodan_ • WHAT IS SERVERLESS? • IS SERVERLESS ONLY ABOUT THE FUNCTIONS • 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?
7. #FDConf @slobodan_
8. #FDConf @slobodan_ 1. WHAT IS
 SERVERLESS?
9. #FDConf @slobodan_ PLATFORM-AS-A-SERVICE (PaaS)
10. #FDConf @slobodan_ FUNCTION-AS-A-SERVICE (FaaS)
11. #FDConf @slobodan_
12. LET’S TRY TO EXPLAIN IT WITH SOMETHING AS SIMPLE AS LEGO BRICKS
13. #FDConf @slobodan_
14. #FDConf @slobodan_ Imagine Lego 4x4 white piece is a server
15. #FDConf @slobodan_ Building and deploying
 monolith app
16. #FDConf @slobodan_ Building and deploying
 monolith app
17. #FDConf @slobodan_ Building and deploying
 monolith app
18. #FDConf @slobodan_ Building and deploying
 monolith app
19. #FDConf @slobodan_ Then people start using it and you need to scale
20. #FDConf @slobodan_ You need to scale everything, but only green and blue parts are really used
21. #FDConf @slobodan_ If one part of the app fails whole system will fail
22. #FDConf @slobodan_ If one part of the app fails whole system will fail
23. #FDConf @slobodan_ MICROSERVICES TO THE RESCUE
24. #FDConf @slobodan_ Hello, from your server, again! Now it can be in the cloud, it doesn’t matter
25. #FDConf @slobodan_ Now each service should be independent, right?
26. #FDConf @slobodan_ Now each service should be independent, right?
27. #FDConf @slobodan_ Now each service should be independent, right?
28. #FDConf @slobodan_ Scaling is easy
29. #FDConf @slobodan_ Scaling is easy
30. #FDConf @slobodan_ Scaling is easy
31. #FDConf @slobodan_ And if no one is using some service it’s simple to remove or replace it
32. #FDConf @slobodan_ And if no one is using some service it’s simple to remove or replace it
33. #FDConf @slobodan_ And if some service fails, it doesn’t affect the system
34. #FDConf @slobodan_ And if some service fails, it doesn’t affect the system
35. #FDConf @slobodan_ But what if we didn’t scale it before it fails?
36. #FDConf @slobodan_ ALSO, ARE SERVERS THAT CHEAP?
37. #FDConf @slobodan_ How do we make microservices cheaper?
38. #FDConf @slobodan_ By bundling them together
39. #FDConf @slobodan_ By bundling them together
40. #FDConf @slobodan_ By bundling them together
41. #FDConf @slobodan_ By bundling them together
42. #FDConf @slobodan_ But what if this one fails?
43. #FDConf @slobodan_ IMAGINE WE DON’T NEED 4X4 PIECE ANYMORE?
44. #FDConf @slobodan_ Imagine our microservices without 4x4 white pieces!
45. #FDConf @slobodan_ Than scaling is simply adding more services
46. #FDConf @slobodan_ And, if we don’t need some service…
47. #FDConf @slobodan_ And, if we don’t need some service…
48. #FDConf @slobodan_ NOW IMAGINE THAT SCALING IS DONE AUTOMATICALLY
49. #FDConf @slobodan_ If something fails it’s replaced automatically
50. #FDConf @slobodan_ ALSO IMAGINE THAT YOU PAY ONLY FOR THE PARTS THAT YOU ARE USING AT THE MOMENT
51. #FDConf @slobodan_
52. #FDConf @slobodan_ WELL, WE CALL THAT THING SERVERLESS!
53. #FDConf @slobodan_
54. #FDConf @slobodan_ 2. IS SERVERLESS ONLY ABOUT THE FUNCTIONS?
55. #FDConf @slobodan_ NO
56. #FDConf @slobodan_ НЕТ
57. #FDConf @slobodan_ SERVERLESS IS A TECHNOLOGY THAT COST YOU NOTHING IF NO-ONE IS USING IT
58. #FDConf @slobodan_ FUNCTIONS ARE JUST A SUBSET OF SERVERLESS
59. #FDConf @slobodan_
60. #FDConf @slobodan_ THIS TALK WILL FOCUS ON SERVERLESS FUNCTIONS
61. #FDConf @slobodan_ 3. HOW DOES IT WORK?
62. #FDConf @slobodan_ EVENT-DRIVEN
63. #FDConf @slobodan_
64. #FDConf @slobodan_
65. #FDConf @slobodan_
66. #FDConf @slobodan_
67. #FDConf @slobodan_
68. #FDConf @slobodan_
69. #FDConf @slobodan_ STATELESS
70. #FDConf @slobodan_ SERVERLESS IS LIKE A GOLDEN FISH
71. #FDConf @slobodan_ BUT WHAT ABOUT REAL SYSTEMS?
72. #FDConf @slobodan_
73. #FDConf @slobodan_
74. #FDConf @slobodan_ SERVERLESS APP
75. #FDConf @slobodan_
76. #FDConf @slobodan_
77. #FDConf @slobodan_
78. #FDConf @slobodan_ IT’S LIKE A BLACK BOX BUT HOW DOES THAT BLACK BOX WORK?
79. #FDConf @slobodan_ exports.handler = (event, context, cb) => { cb(null, { “Hello”: ”World” }) }
80. #FDConf @slobodan_ JSON event { “body”:”…”, “headers”: “”, … } exports.handler = (event, context, cb) => { cb(null, { “Hello”: ”World” }) }
81. #FDConf @slobodan_ JSON { “body”: { “Hello”:”World” }, “status”: 200, … } exports.handler = (event, context, cb) => { cb(null, { “Hello”: ”World” }) }
82. #FDConf @slobodan_
83. #FDConf @slobodan_ 4. WHAT ARE THE MOST IMPORTANT SERVERLESS PLATFORMS TODAY?
84. #FDConf @slobodan_
85. #FDConf @slobodan_
86. #FDConf @slobodan_
87. #FDConf @slobodan_ AWS LAMBDA
88. #FDConf @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
89. #FDConf @slobodan_ • TIMEOUT UP TO 300 SECONDS • 128MB TO 1.5GB OF MEMORY • 500MB OF NON-PERSISTENT STORAGE (/TMP) • DEFAULT CONCURRENT EXECUTION LIMIT: 1000
90. #FDConf @slobodan_ WHAT PROGRAMMING LANGUAGE YOU NEED TO USE FOR SERVERLESS?
91. #FDConf @slobodan_ • NODE.JS • PYTHON • JAVA • C# • SHELL SCRIPTS • ANY EXECUTABLE AWS LAMBDA
92. #FDConf @slobodan_ • NODE.JS • C# • F# • PYHON • PHP • SHELL SCRIPTS • ANY EXECUTABLE AZURE FUNCTIONS
93. #FDConf @slobodan_ GOOGLE CODE FUNCTIONS JUST NODE.JS AT THE MOMENT
94. #FDConf @slobodan_
95. 5. HOW DOES IT WORK WITH NODE.JS?
96. #FDConf @slobodan_
97. #FDConf @slobodan_ • GOOD STARTUP PERFORMANCE • SMALL MODULES • PERFORMANCE WITH LOW CPU AND MEMORY • SINGLE THREAD • EASY TO LEARN PROS
98. #FDConf @slobodan_ • ASYNC • MADE FOR SCALABILITY • NODE_MODULES SIZE • EASY TO FUCKUP CONS
99. #FDConf @slobodan_ ‘use strict’ console.log(‘Loading event’) exports.handler = (event, context, callback) => { console.log(‘“Hello”: ”World”’) callback(null, {“Hello”: ”World”}) } hello-world.js
100. #FDConf @slobodan_ ‘use strict’ console.log(‘Loading event’) exports.handler = (event, context, callback) => { console.log(‘“Hello”: ”World”’) callback(null, {“Hello”: ”World”}) } hello-world.js
101. #FDConf @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
102. #FDConf @slobodan_ IT’S LIKE FLYING FROM MINSK TO HAWAII WITH LOW-COST DESTINATION IS AWESOME, BUT IT TAKES SOME TIME AND IT’S NOT THAT PLEASANT
103. #FDConf @slobodan_ • SERVERLESS FRAMEWORK • CLAUDIA.JS • AMAZON SAM • APEX FRAMEWORKS / LIBRARIES
104. #FDConf @slobodan_ CLAUDIAJS.COM > 110.000 DOWNLOADS
105. #FDConf @slobodan_ CLAUDIA VS NATIVE UPLOAD === PRIVATE JET VS LOW-COST WITH A FEW LAYOVERS
106. #FDConf @slobodan_
107. #FDConf @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
108. #FDConf @slobodan_ FLAT LEARNING CURVE HOW FAST CAN WE START?
109. #FDConf @slobodan_
110. #FDConf @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
111. #FDConf @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const frameworks = require(‘./frameworks.json’) api.get(‘/‘, () => frameworks) module.exports = api api.js
112. #FDConf @slobodan_ claudia create \ --region eu-central-1 \ --api-module api DEPLOY
113. #FDConf @slobodan_ { "lambda": { "role": “js-frameworks-executor", "name": "js-frameworks", "region": "eu-central-1" }, "api": { "id": "h2gcdkdys7", "module": "api", "url": "https://h2gcdkdys7.execute-api.eu- central-1.amazonaws.com/latest" } } RESULT
114. #FDConf @slobodan_ bit.ly/js-frameworks-api
115. #FDConf @slobodan_ bit.ly/js-frameworks-api
116. #FDConf @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const frameworks = require(‘./fun-facts.json’) api.get(‘/‘, () => frameworks) api.get(‘/{id}’, req => frameworks.filter(framework => framework.id === req.pathParams.id )) api.get(‘/random‘, () => frameworks[ Math.floor(Math.random() * frameworks.length) ]) module.exports = api api.js
117. #FDConf @slobodan_ api.js ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const frameworks = require(‘./fun-facts.json’) api.get(‘/‘, () => frameworks) api.get(‘/{id}’, req => frameworks.filter(framework => framework.id === req.pathParams.id )) api.get(‘/random‘, () => frameworks[ Math.floor(Math.random() * frameworks.length) ]) module.exports = api
118. #FDConf @slobodan_ claudia update UPDATE
119. #FDConf @slobodan_ /random bit.ly/js-frameworks-api
120. #FDConf @slobodan_ /8 bit.ly/js-frameworks-api
121. #FDConf @slobodan_
122. #FDConf @slobodan_ 6. HOW TO DEBUG SERVERLESS FUNCTION
123. #FDConf @slobodan_ WHERE CAN YOU SEE
 CONSOLE.LOG?
124. #FDConf @slobodan_ CLOUD WATCH
125. #FDConf @slobodan_ MONITORING SERVICE FOR AWS CLOUD RESOURCES AND THE APPS YOU RUN ON AWS
126. #FDConf @slobodan_ YOU CAN USE IT VIA WEB CONSOLE, AWS CLI, ETC.
127. #FDConf @slobodan_ api.get(‘/{id}’, req => { const filtered = frameworks.filter(framework => framework.id === req.pathParams.id ) console.log(‘Here >>’, filtered) return filtered }) api.js
128. #FDConf @slobodan_ aws logs filter-log-events \ --filter='Log this' \ —log-group-name=/aws/lambda/js-frameworks \ --query='events[0].message' \ --output=text LIST LOG COMMAND
129. #FDConf @slobodan_ 2017-09-16T07:25:12.652Z 2d4ea5c2-9ab0-11e7-96c6-7d019d1c743c Log this [] OUTPUT
130. #FDConf @slobodan_ DEBUGGING IS NOT FUN. HOW CAN WE DO LESS DEBUGGING?
131. #FDConf @slobodan_ BY WRITING TESTS
132. #FDConf @slobodan_ BUT HOW DO YOU TEST SERVERLESS FUNCTIONS?
133. #FDConf @slobodan_ AS ANY OTHER NODE.JS LIBRARY !
134. #FDConf @slobodan_ EXAMPLE? CLAUDIA-BOT-BUILDER SPECS
135. #FDConf @slobodan_ AWS X RAY
136. #FDConf @slobodan_
137. #FDConf @slobodan_
138. #FDConf @slobodan_ FUNNIEST WAY TO TRY SERVERLESS? "
139. #FDConf @slobodan_ SERVERLESS.CAMP
140. #FDConf @slobodan_ EASIEST WAY TO LEARN SERVERLESS? GO AND PLAY WITH IT!
141. #FDConf @slobodan_ FOLLOW ME ON TWITTER FOR MORE INFO - @SLOBODAN_
142. #FDConf @slobodan_ • CREATE AN API • CONNECT WITH DYNAMODB • ADD AUTHORIZATION • CONVERT IMAGES • BUILD A CHATBOT • LEARN HOW TO TEST AND DEBUG • LEARN GOOD ARCHITECTURE PRACTICES • MIGRATE EXPRESS APP TO SERVERLESS
143. #FDConf @slobodan_
144. #FDConf @slobodan_ 7. WHY IS IT IMPORTANT?
145. #FDConf @slobodan_ MINIMAL MAINTENANCE
146. #FDConf @slobodan_ FINANCIAL INCENTIVE https://gojko.net/2016/08/27/serverless.html
147. #FDConf @slobodan_ TRUE MICROSERVICES
148. #FDConf @slobodan_ AUTO SCALING AND FAILOVER
149. #FDConf @slobodan_ FOCUS ON BUSINESS LOGIC, NOT CONFIGURATION
150. #FDConf @slobodan_
151. #FDConf @slobodan_ 8. WHEN SHOULD I USE SERVERLESS?
152. #FDConf @slobodan_ LET’S START WITH WHEN YOU SHOULD NOT USE SERVERLESS?
153. #FDConf @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
154. #FDConf @slobodan_ OK, BUT WHAT IS IT GOOD FOR?
155. #FDConf @slobodan_ • WEB APIs • BACKEND FOR THE SINGLE PAGE APP • CHATBOTS • QUICK PROTOTYPES THAT CAN EVOLVE TO 
 A REAL SOLUTIONS • PROCESSING FILES OR ANY KIND OF DATA • IoT • MICROSERVICES • MANY, MANY OTHER THINGS
156. #FDConf @slobodan_ 8 1/2. WAIT, WHAT ABOUT THE NAME?
157. #FDConf @slobodan_
158. #FDConf @slobodan_ LESS IS MORE
159. #FDConf @slobodan_ LESS IS MORE SERVER
160. #FDConf @slobodan_ LESS IS MORE SERVER SERVERS
161. #FDConf @slobodan_ “SERVERLESS” IS JUST A NAME. WE COULD HAVE CALLED IT “JEFF” PAUL JOHNSTON
162. #FDConf @slobodan_ “IT IS SERVERLESS THE SAME WAY WIFI IS WIRELESS” GOJKO ADŽIĆ
163. #FDConf @slobodan_ BONUS: IS THERE SERVERLESS FOR FRONT-END?
164. #FDConf @slobodan_ ДА!
165. #FDConf @slobodan_
166. #FDConf @slobodan_
167. #FDConf @slobodan_
168. #FDConf @slobodan_ npm i scottyjs -g
169. #FDConf @slobodan_ • SERVERLESS IS A TECHNOLOGY THAT COST YOU NOTHING IF NO-ONE IS USING IT • IT’S MORE THAN FUNCTIONS • FULLY MANAGED • FUNCTIONS ARE EVENT-DRIVEN - MANY TRIGGERS • AUTO SCALING AND AUTO FAILOVER • IT WORKS NICE WITH NODE.JS • IT’S TRICKY TO DEBUG, SO WRITE TESTS SUMMARY
170. #FDConf @slobodan_ ALSO, SERVERS STILL EXIST BUT THEY ARE NOT YOUR PROBLEM
171. #FDConf @slobodan_
172. #FDConf @slobodan_ FOLLOW ME ON TWITTER FOR MORE INFO - @SLOBODAN_
173. #FDConf @slobodan_ THAT'S IT.
 THANKS!
174. #FDConf @slobodan_ КОНЕЦ
175. #FDConf @slobodan_ QUESTIONS? @slobodan_ bit.ly/fdconf-serverless #FDConf