The Hitchhikers Guide To The Serverless Galaxy - AmsterdamJS

My presentation from AmsterdamJS 2017

Transcript

1. GUIDE TO THE SERVERLESS GALAXY HITCHHIKER'S THE
2. #amsterdamjs @slobodan_ OUR TOUR FOR TODAY
3. #amsterdamjs @slobodan_ • WHAT IS SERVERLESS • HOW DOES IT WORK • HOW DOES IT WORK WITH NODE.JS • WHY IS IT IMPORTANT • WHEN SHOULD YOU USE IT
4. #amsterdamjs @slobodan_ YOUR TOUR GUIDE
5. #amsterdamjs @slobodan_ CTO AT CLOUD HORIZON AND JS BELGRADE MEETUP ORGANIZER github.com/stojanovic twitter.com/slobodan_ SLOBODAN STOJANOVIĆ
6. #amsterdamjs @slobodan_ ANOTHER SERVERLESS TALK?
7. #amsterdamjs @slobodan_ “JUST BELIEVE EVERYTHING I TELL YOU, AND IT WILL ALL BE VERY, VERY SIMPLE” AH, WELL, I'M NOT SURE I BELIEVE THAT
8. #amsterdamjs @slobodan_ WHAT IS SERVERLESS? EXCEPT A BUZZWORD, OF COURSE
9. #amsterdamjs @slobodan_ PLATFORM-AS-A-SERVICE (PaaS)
10. #amsterdamjs @slobodan_ FUNCTION-AS-A-SERVICE (FaaS)
11. #amsterdamjs @slobodan_
12. #amsterdamjs @slobodan_ LET’S TRY TO EXPLAIN IT WITH SOMETHING AS SIMPLE AS LEGO BRICKS
13. #amsterdamjs @slobodan_
14. #amsterdamjs @slobodan_ Imagine Lego 4x4 white piece is a physical server
15. #amsterdamjs @slobodan_ Building and deploying
 monolith app
16. #amsterdamjs @slobodan_ Building and deploying
 monolith app
17. #amsterdamjs @slobodan_ Then people start using it and you need to scale
18. #amsterdamjs @slobodan_ Then people start using it and you need to scale
19. #amsterdamjs @slobodan_ You need to scale everything, but only green and blue parts are really used
20. #amsterdamjs @slobodan_ If one part of the app fails whole system will fail
21. #amsterdamjs @slobodan_ If one part of the app fails whole system will fail
22. #amsterdamjs @slobodan_ If one part of the app fails whole system will fail
23. #amsterdamjs @slobodan_ MICROSERVICES TO THE RESCUE
24. #amsterdamjs @slobodan_ Hello, from our physical server, again! Now it can be in the cloud, it doesn’t matter
25. #amsterdamjs @slobodan_ Now each service should be independent, right?
26. #amsterdamjs @slobodan_ Now each service should be independent, right?
27. #amsterdamjs @slobodan_ Scaling is easy
28. #amsterdamjs @slobodan_ Scaling is easy
29. #amsterdamjs @slobodan_ And if no one is using some service it’s simple to remove or replace it
30. #amsterdamjs @slobodan_ And if no one is using some service it’s simple to remove or replace it
31. #amsterdamjs @slobodan_ And if some service fails, it doesn’t affect the system
32. #amsterdamjs @slobodan_ And if some service fails, it doesn’t affect the system
33. #amsterdamjs @slobodan_ And if some service fails, it doesn’t affect the system
34. #amsterdamjs @slobodan_ But what if we didn’t scale it before it fails?
35. #amsterdamjs @slobodan_ ALSO, ARE SERVERS THAT CHEAP?
36. #amsterdamjs @slobodan_ How do we make microservices cheaper?
37. #amsterdamjs @slobodan_ By bundling them together
38. #amsterdamjs @slobodan_ By bundling them together
39. #amsterdamjs @slobodan_ By bundling them together
40. #amsterdamjs @slobodan_ By bundling them together
41. #amsterdamjs @slobodan_ By bundling them together
42. #amsterdamjs @slobodan_ But what if this one fails?
43. #amsterdamjs @slobodan_ IMAGINE WE DON’T NEED 4X4 PIECE ANYMORE?
44. #amsterdamjs @slobodan_ Imagine our microservices without 4x4 white pieces!
45. #amsterdamjs @slobodan_ Imagine our microservices without 4x4 white pieces!
46. #amsterdamjs @slobodan_ Than scaling is simply adding more services
47. #amsterdamjs @slobodan_ And, if we don’t need some service…
48. #amsterdamjs @slobodan_ And, if we don’t need some service…
49. #amsterdamjs @slobodan_ NOW IMAGINE THAT SCALING IS DONE AUTOMATICALLY
50. #amsterdamjs @slobodan_ If something fails it’s replaced automatically
51. #amsterdamjs @slobodan_ ALSO IMAGINE THAT YOU PAY ONLY FOR THE PARTS THAT YOU ARE USING AT THE MOMENT
52. #amsterdamjs @slobodan_
53. #amsterdamjs @slobodan_ WELL, WE CALL THAT THING SERVERLESS!
54. #amsterdamjs @slobodan_
55. #amsterdamjs @slobodan_ LESS IS MORE
56. #amsterdamjs @slobodan_ LESS IS MORE SERVER SERVERS
57. #amsterdamjs @slobodan_ “SERVERLESS” IS JUST A NAME. WE COULD HAVE CALLED IT “JEFF” PAUL JOHNSTON
58. #amsterdamjs @slobodan_ “IT IS SERVERLESS THE SAME WAY WIFI IS WIRELESS” GOJKO ADŽIĆ
59. #amsterdamjs @slobodan_ “WE ARE STUCK WITH TECHNOLOGY WHEN WHAT WE REALLY WANT IS JUST STUFF THAT WORKS”
60. #amsterdamjs @slobodan_ HOW DOES IT WORK? IS IT MAGIC?
61. #amsterdamjs @slobodan_ EVENT-DRIVEN
62. #amsterdamjs @slobodan_
63. #amsterdamjs @slobodan_
64. #amsterdamjs @slobodan_
65. #amsterdamjs @slobodan_
66. #amsterdamjs @slobodan_
67. #amsterdamjs @slobodan_
68. #amsterdamjs @slobodan_
69. #amsterdamjs @slobodan_
70. #amsterdamjs @slobodan_
71. #amsterdamjs @slobodan_
72. #amsterdamjs @slobodan_
73. #amsterdamjs @slobodan_
74. #amsterdamjs @slobodan_ “LIGHTBULB” == FUNCTION
75. #amsterdamjs @slobodan_ STATELESS
76. #amsterdamjs @slobodan_ SERVERLESS IS LIKE A GOLDFISH
77. #amsterdamjs @slobodan_ BUT WHAT ABOUT REAL SYSTEMS?
78. #amsterdamjs @slobodan_
79. #amsterdamjs @slobodan_
80. #amsterdamjs @slobodan_ SERVERLESS APP
81. #amsterdamjs @slobodan_
82. #amsterdamjs @slobodan_
83. #amsterdamjs @slobodan_
84. #amsterdamjs @slobodan_ IT’S LIKE A BLACK BOX
85. #amsterdamjs @slobodan_ IT’S LIKE A BLACK BOX BUT HOW DOES THAT BLACK BOX WORK?
86. #amsterdamjs @slobodan_ exports.handler = (event, context, callback) => { callback(null, {“Hello”: ”World”}) }
87. #amsterdamjs @slobodan_ JSON event { “body”:”…”, “headers”: “”, … } exports.handler = (event, context, callback) => { callback(null, {“Hello”: ”World”}) }
88. #amsterdamjs @slobodan_ exports.handler = (event, context, callback) => { callback(null, {“Hello”: ”World”}) } JSON { “body”: { “Hello”:”World” }, “status”: 200, … }
89. #amsterdamjs @slobodan_ “REALITY IS FREQUENTLY INACCURATE”
90. #amsterdamjs @slobodan_ HOW DOES IT WORK WITH NODE.JS 0.1 + 0.2
91. #amsterdamjs @slobodan_
92. #amsterdamjs @slobodan_ • GOOD STARTUP PERFORMANCE • SMALL MODULES • PERFORMANCE WITH LOW CPU AND MEMORY • SINGLE THREAD • EASY TO LEARN PROS
93. #amsterdamjs @slobodan_ • ASYNC • MADE FOR SCALABILITY • NODE_MODULES SIZE • EASY TO FUCKUP CONS
94. #amsterdamjs @slobodan_ ‘use strict’ console.log(‘Loading event’) exports.handler = (event, context, callback) => { console.log(‘“Hello”: ”World”’) callback(null, {“Hello”: ”World”}) } hello-world.js
95. #amsterdamjs @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
96. #amsterdamjs @slobodan_ • SERVERLESS FRAMEWORK • CLAUDIA.JS • APEX FRAMEWORKS
97. #amsterdamjs @slobodan_ CLAUDIAJS.COM > 69.000 DOWNLOADS
98. #amsterdamjs @slobodan_
99. #amsterdamjs @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
100. #amsterdamjs @slobodan_ FLAT LEARNING CURVE HOW FAST CAN WE START?
101. #amsterdamjs @slobodan_
102. #amsterdamjs @slobodan_ • npm i claudia -g • SET UP AWS CREDENTIALS (ONE TIME) • mkdir amsterdam-facts && cd $_ • npm init -f • npm i claudia-api-builder -S prepare
103. #amsterdamjs @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const facts = require(‘./amsterdam.json’) api.get(‘/‘, () => facts) module.exports = api api.js
104. #amsterdamjs @slobodan_ claudia create \ --region eu-central-1 \ --api-module api DEPLOY
105. #amsterdamjs @slobodan_ { "lambda": { "role": "amsterdamjs-demo-executor", "name": "amsterdamjs-demo", "region": "eu-central-1" }, "api": { "id": "oocgxwew1l", "module": "api", "url": "https://oocgxwew1l.execute-api.eu- central-1.amazonaws.com/latest" } } RESULT
106. #amsterdamjs @slobodan_ bit.ly/amsterdam-facts
107. #amsterdamjs @slobodan_ bit.ly/amsterdam-facts
108. #amsterdamjs @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const facts = require(‘./amsterdam.json’) api.get(‘/‘, () => facts) api.get(‘/{id}’, req => facts.filter(fact => fact.id === req.pathParams.id )) api.get(‘/random‘, () => facts[ Math.floor(Math.random() * facts.length) ]) module.exports = api api.js
109. #amsterdamjs @slobodan_ ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const facts = require(‘./amsterdam.json’) api.get(‘/‘, () => facts) api.get(‘/{id}’, req => facts.filter(fact => fact.id === req.pathParams.id )) api.get(‘/random‘, () => facts[ Math.floor(Math.random() * facts.length) ]) module.exports = api api.js
110. #amsterdamjs @slobodan_ claudia update UPDATE
111. #amsterdamjs @slobodan_ /random bit.ly/amsterdam-facts
112. #amsterdamjs @slobodan_ /14 bit.ly/amsterdam-facts
113. #amsterdamjs @slobodan_ github.com/stojanovic/amsterdam-facts
114. #amsterdamjs @slobodan_ HOW CAN YOU LEARN SERVERLESS
115. #amsterdamjs @slobodan_
116. #amsterdamjs @slobodan_ EASIEST WAY TO LEARN SERVERLESS? GO AND PLAY WITH IT!
117. #amsterdamjs @slobodan_ FUNNIEST WAY TO LEARN SERVERLESS? !
118. #amsterdamjs @slobodan_ SERVERLESS.CAMP
119. #amsterdamjs @slobodan_
120. #amsterdamjs @slobodan_ “THE ULTIMATE ANSWER TO LIFE, THE UNIVERSE AND EVERYTHING IS...”
121. #amsterdamjs @slobodan_ WHY IS IT IMPORTANT? AND WHY IS IT IMPORTANT FOR YOU
122. #amsterdamjs @slobodan_ MINIMAL MAINTENANCE
123. #amsterdamjs @slobodan_ FINANCIAL INCENTIVE https://gojko.net/2016/08/27/serverless.html
124. #amsterdamjs @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
125. #amsterdamjs @slobodan_ TRUE MICROSERVICES
126. #amsterdamjs @slobodan_ AUTO SCALING AND FAILOVER
127. #amsterdamjs @slobodan_ FOCUS ON BUSINESS LOGIC, NOT CONFIGURATION
128. #amsterdamjs @slobodan_ “IT IS A MISTAKE TO THINK YOU CAN SOLVE ANY MAJOR PROBLEMS JUST WITH POTATOES”
129. #amsterdamjs @slobodan_ LET’S START WITH WHEN YOU SHOULD NOT USE SERVERLESS?
130. #amsterdamjs @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
131. #amsterdamjs @slobodan_ OK, BUT WHAT IS IT GOOD FOR?
132. #amsterdamjs @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
133. #amsterdamjs @slobodan_ HOW CAN YOU START USING IT TODAY?
134. #amsterdamjs @slobodan_ SIDE PROJECT OR SOMETHING SMALL AWS LAMBDA + AWS ECOSYSTEM
135. #amsterdamjs @slobodan_ MOVE SOME NON-ESSENTIAL FEATURE TO SERVERLESS EXISTING APP + FEATURE IN AWS LAMBDA
136. #amsterdamjs @slobodan_
137. #amsterdamjs @slobodan_ “TO SUMMARIZE THE SUMMARY OF THE SUMMARY: PEOPLE ARE A PROBLEM”
138. #amsterdamjs @slobodan_ IS IT SECURE? IF WE HAVE TIME "
139. #amsterdamjs @slobodan_
140. #amsterdamjs @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
141. #amsterdamjs @slobodan_ • BAD CODE • BAD PERMISSIONS • 3RD PARTY LIBRARIES • PROBLEMS WITH OTHER BUILDING BLOCKS,
 SUCH AS SQL INJECTION • KEYS AND SECRETS PROBLEMS
142. #amsterdamjs @slobodan_ SO, IS IT SECURE? IT DEPENDS ON YOU
143. #amsterdamjs @slobodan_ THERE ARE VULNERABLE PARTS, BUT IT’S A BETTER SET OF PROBLEMS TO DEAL WITH
144. #amsterdamjs @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 • GO AND TRY IT, IT’S EASY TO LEARN # SUMMARY
145. #amsterdamjs @slobodan_
146. #amsterdamjs @slobodan_ ALSO, SERVERS STILL EXIST BUT THEY ARE NOT YOUR PROBLEM
147. #amsterdamjs @slobodan_ THE END
148. #amsterdamjs @slobodan_ HET EINDE
149. #amsterdamjs @slobodan_ QUESTIONS? @SLOBODAN_ http://bit.ly/amsterdamjs-serverless #AMSTERDAMJS