The Hitchhikers Guide To The Serverless Galaxy - CodeEurope 2017, Wroclaw and Warsaw

"The Hitchhikers Guide To The Serverless Galaxy" presentation from CodeEurope 2017 conference in Wroclaw and Warsaw:

https://www.codeeurope.pl/en/speakers/slobodan-stojanovic

Transcript

1. GUIDE TO THE SERVERLESS GALAXY HITCHHIKER'S THE
2. #codeeurope OUR TOUR FOR TODAY
3. #codeeurope • WHAT IS SERVERLESS • HOW DOES IT WORK • WHY IS IT IMPORTANT • SERVERLESS PLATFORMS • WHEN SHOULD YOU USE IT • HOW DOES IT WORK WITH NODE.JS
4. #codeeurope YOUR TOUR GUIDE
5. #codeeurope CTO AT CLOUD HORIZON AND JS BELGRADE MEETUP ORGANIZER github.com/stojanovic twitter.com/slobodan_ SLOBODAN STOJANOVIĆ
6. #codeeurope “JUST BELIEVE EVERYTHING I TELL YOU, AND IT WILL ALL BE VERY, VERY SIMPLE” AH, WELL, I'M NOT SURE I BELIEVE THAT
7. #codeeurope WHAT IS SERVERLESS? EXCEPT A BUZZWORD, OF COURSE
8. #codeeurope PLATFORM-AS-A-SERVICE (PaaS)
9. #codeeurope FUNCTION-AS-A-SERVICE (FaaS)
10. #codeeurope LET’S TRY TO EXPLAIN IT WITH SOMETHING AS SIMPLE AS LEGO BRICKS
11. #codeeurope
12. #codeeurope Imagine Lego 4x4 white piece is a physical server
13. #codeeurope Building and deploying
 monolith app
14. #codeeurope Building and deploying
 monolith app
15. #codeeurope Then people start using it and you need to scale
16. #codeeurope You need to scale everything, but only green and blue parts are really used
17. #codeeurope If one part of the app fails whole system will fail
18. #codeeurope If one part of the app fails whole system will fail
19. #codeeurope If one part of the app fails whole system will fail
20. #codeeurope MICROSERVICES TO THE RESCUE
21. #codeeurope Hello, from our physical server, again! Now it can be in the cloud, it doesn’t matter
22. #codeeurope Now each service should be independent, right?
23. #codeeurope Now each service should be independent, right?
24. #codeeurope Scaling is easy
25. #codeeurope And if no one is using some service it’s simple to remove or replace it
26. #codeeurope And if no one is using some service it’s simple to remove or replace it
27. #codeeurope And if some service fails, it doesn’t affect the system
28. #codeeurope And if some service fails, it doesn’t affect the system
29. #codeeurope And if some service fails, it doesn’t affect the system
30. #codeeurope But what if we didn’t scaled it before it fails?
31. #codeeurope ALSO, ARE SERVERS THAT CHEAP? #codeeurope
32. #codeeurope How do we make microservices cheaper?
33. #codeeurope By bundling them together
34. #codeeurope By bundling them together
35. #codeeurope By bundling them together
36. #codeeurope By bundling them together
37. #codeeurope But what if this one fails?
38. #codeeurope IMAGINE WE DON’T NEED 4X4 PIECE ANYMORE?
39. #codeeurope Imagine our microservices without 4x4 white pieces!
40. #codeeurope Imagine our microservices without 4x4 white pieces!
41. #codeeurope Than scaling is simply adding more services
42. #codeeurope Than scaling is simply adding more services
43. #codeeurope And, if we don’t need some service…
44. #codeeurope And, if we don’t need some service…
45. #codeeurope NOW IMAGINE THAT SCALING IS DONE AUTOMATICALLY #codeeurope
46. #codeeurope If something fails it’s replaced automatically
47. #codeeurope If something fails it’s replaced automatically
48. #codeeurope If something fails it’s replaced automatically
49. #codeeurope ALSO IMAGINE THAT YOU PAY ONLY FOR THE PARTS THAT YOU ARE USING AT THE MOMENT
50. #codeeurope
51. #codeeurope WELL, WE CALL THAT THING SERVERLESS!
52. #codeeurope “WE ARE STUCK WITH TECHNOLOGY WHEN WHAT WE REALLY WANT IS JUST STUFF THAT WORKS”
53. #codeeurope HOW DOES IT WORK? IS IT MAGIC?
54. #codeeurope “WOULD IT SAVE YOU A LOT OF TIME IF I JUST GAVE UP AND WENT MAD NOW?”
55. #codeeurope EVENT-DRIVEN
56. #codeeurope
57. #codeeurope
58. #codeeurope
59. #codeeurope
60. #codeeurope
61. #codeeurope
62. #codeeurope
63. #codeeurope
64. #codeeurope
65. #codeeurope
66. #codeeurope
67. #codeeurope “LIGHTBULB” == FUNCTION
68. #codeeurope BUT WHAT ABOUT REAL SYSTEMS?
69. #codeeurope
70. #codeeurope
71. #codeeurope SERVERLESS APP
72. #codeeurope
73. #codeeurope
74. #codeeurope • HTTP REQUEST • FILE • NOTIFICATION • MAIL • STREAM • MANY OTHER THINGS WHAT CAN TRIGGER SERVERLESS FUNCTION
75. #codeeurope “THE ULTIMATE ANSWER TO LIFE, THE UNIVERSE AND EVERYTHING IS...”
76. #codeeurope WHY IS IT IMPORTANT? AND WHY IS IT IMPORTANT FOR YOU
77. #codeeurope FINANCIAL INCENTIVE https://gojko.net/2016/08/27/serverless.html
78. #codeeurope TRUE MICROSERVICES
79. #codeeurope AUTO SCALING AND FAILOVER
80. #codeeurope FOCUS ON BUSINESS LOGIC, NOT CONFIGURATION
81. #codeeurope “SO LONG, AND THANKS FOR ALL THE FISH” FISH”
82. #codeeurope “SO LONG, AND THANKS FOR ALL THE FISH” SERVERS”
83. #codeeurope SERVERLESS PLATFORMS LET’S SEE WHAT’S ON THE MENU TODAY
84. #codeeurope
85. #codeeurope
86. #codeeurope AWS LAMBDA
87. #codeeurope • TIMEOUT BETWEEN 1 AND 300 SECONDS • 128MB TO 1.5GB OF MEMORY • 500MB OF NON-PERSISTENT STORAGE (/TMP) • DEFAULT CONCURRENT EXECUTION LIMIT: 1000
88. #codeeurope • $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. #codeeurope LAMBDA @ EDGE
90. #codeeurope WHAT PROGRAMMING LANGUAGE YOU NEED TO USE FOR SERVERLESS?
91. #codeeurope • NODE.JS • PYTHON • JAVA • C# • SHELL SCRIPTS • ANY EXECUTABLE AWS LAMBDA
92. #codeeurope • NODE.JS • C# • F# • PYHON • PHP • SHELL SCRIPTS • ANY EXECUTABLE AZURE FUNCTIONS
93. #codeeurope GOOGLE CODE FUNCTIONS JUST NODE.JS AT THE MOMENT
94. #codeeurope “IT IS A MISTAKE TO THINK YOU CAN SOLVE ANY MAJOR PROBLEMS JUST WITH POTATOES”
95. #codeeurope WHEN SHOULD YOU USE IT? AND, EVEN MORE IMPORTANT, WHEN NOT TO USE IT
96. #codeeurope • 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
97. #codeeurope HOW CAN YOU START USING IT?
98. #codeeurope SIDE PROJECT OR SOMETHING SMALL AWS LAMBDA + AWS ECOSYSTEM
99. #codeeurope MOVE SOME NON-ESSENTIAL FEATURE TO SERVERLESS EXISTING APP + FEATURE IN AWS LAMBDA
100. #codeeurope
101. #codeeurope HOW DOES IT WORK WITH NODE.JS 0.1 + 0.2
102. #codeeurope
103. #codeeurope • GOOD STARTUP PERFORMANCE • SMALL MODULES • PERFORMANCE WITH LOW CPU AND MEMORY • SINGLE THREAD • EASY TO LEARN PROS
104. #codeeurope • ASYNC • MADE FOR SCALABILITY • NODE_MODULES SIZE • EASY TO FUCKUP CONS
105. #codeeurope ‘use strict’ console.log(‘Loading event’) exports.handler = (event, context, callback) => { console.log(‘“Hello”: ”World”’) callback(null, {“Hello”: ”World”}) } hello-world.js
106. #codeeurope • 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
107. #codeeurope • SERVERLESS FRAMEWORK • CLAUDIA.JS • APEX FRAMEWORKS
108. #codeeurope CLAUDIAJS.COM > 65.000 DOWNLOADS
109. #codeeurope
110. #codeeurope • DEPLOY AND UPDATE WITH SINGLE COMMAND • USE STANDARD NPM MODULES • NO BOILERPLATE, JUST FOCUS ON YOUR WORK • MANAGE MULTIPLE VERSIONS EASILY • GET STARTED QUICKLY, LOW LEARNING CURVE MAIN CHARACTERISTICS
111. #codeeurope LOW LEARNING CURVE HOW FAST CAN WE START?
112. #codeeurope • npm i claudia -g • SET UP AWS CREDENTIALS (ONE TIME) • mkdir claudia-api && cd $_ • npm init -f • npm i claudia-api-builder -S • npm i huh -S prepare
113. #codeeurope ‘use strict’ const Api = require(‘claudia-api-builder‘) const api = new Api() const excuse = require(‘huh’) api.get(‘/‘, () => { return excuse.get() }) module.exports = api api.js
114. #codeeurope { "lambda": { "role": "codeeurope-executor", "name": "codeeurope", "region": "eu-central-1" }, "api": { "id": "d1weoszyg7", "module": "api", "url": "https://d1weoszyg7.execute-api.eu central-1.amazonaws.com/latest" } } result
115. #codeeurope http://bit.ly/2pfNjGL
116. #codeeurope http://bit.ly/2pfNjGL
117. #codeeurope OUR TOUR FOR TODAY IS DONE IS IT?
118. #codeeurope “FOR A MOMENT, NOTHING HAPPENED.
119. #codeeurope “FOR A MOMENT, NOTHING HAPPENED. THEN, AFTER A SECOND OR SO, NOTHING CONTINUED TO HAPPEN.”
120. #codeeurope ONE MORE THING… ACTUALLY, LET’S MAKE IT TWO MORE THINGS
121. #codeeurope “REALITY IS FREQUENTLY INACCURATE”
122. #codeeurope WHAT ABOUT THE NAME? BONUS #1
123. #codeeurope LESS IS MORE
124. #codeeurope LESS IS MORE SERVER SERVERS
125. #codeeurope
126. #codeeurope 2012
127. #codeeurope “WHY THE FUTURE OF SOFTWARE AND APPS IS SERVERLESS” BY KEN FROMM
128. #codeeurope 2014
129. #codeeurope AWS LAMBDA
130. #codeeurope 2015
131. #codeeurope API GATEWAY
132. #codeeurope “SERVERS ARE DEAD..” BY ANT STANLEY
133. #codeeurope “SERVERS ARE DEAD..” BY ANT STANLEY
134. #codeeurope JAWS BECOMES SERVERLESS FRAMEWORK
135. #codeeurope 2016
136. #codeeurope “SERVERLESS” IS JUST A NAME. WE COULD HAVE CALLED IT “JEFF” PAUL JOHNSTON
137. #codeeurope NOW
138. #codeeurope SERVERLESS IS EVERYWHERE
139. #codeeurope “TO SUMMARIZE THE SUMMARY OF THE SUMMARY: PEOPLE ARE A PROBLEM”
140. #codeeurope IS IT SECURE? BONUS #2
141. #codeeurope
142. #codeeurope • 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
143. #codeeurope • BAD CODE • BAD PERMISSIONS • 3RD PARTY LIBRARIES • PROBLEMS WITH OTHER BUILDING BLOCKS,
 SUCH AS SQL INJECTION • KEYS AND SECRETS PROBLEMS
144. #codeeurope SO, IS IT SECURE? IT DEPENDS ON YOU
145. #codeeurope THERE ARE VULNERABLE PARTS, BUT IT’S A BETTER SET OF PROBLEMS TO DEAL WITH
146. #codeeurope THE END
147. #codeeurope KONIEC
148. #codeeurope QUESTIONS? @SLOBODAN_ BIT.LY/… #CODEEUROPE