Working with Serverless in 2017

This presentation is about the challenges me team faced while working with serverless architecture.
What we have learned, what were the obstacles and the benefits.

Transcript

1. #SERVERLESS
2. WHO AM I?
4. WHAT DOES SERVERLESS MEAN?
5. THE PHRASE “SERVERLESS” DOESN’T MEAN SERVERS ARE NO LONGER INVOLVED. IT SIMPLY MEANS THAT DEVELOPERS NO LONGER HAVE TO THINK "THAT MUCH" ABOUT THEM https://www.quora.com/What-is-serverless-computing
6. TL;DR A SERVERLESS SOLUTION IS ONE THAT COSTS YOU NOTHING TO RUN IF NOBODY IS USING IT (EXCLUDING DATA STORAGE) Paul Johnston
7. SO YOU WANT TO BUILD YOUR OWN SERVERLESS PLATFORM. FIRST STEP. GET SOME SERVERS. Kelsey Hightower TEXT
8. ‣Confuse ‣Focus on solving problems ‣No cloud only other people’s computers ‣Components ‣Available when your functions are down ‣Throughput dynamo costs
9. SERVERLESS VS FAAS
10. SERVERLESS IS EQUAL TO BAAS FAAS
11. FAAS
12. SERVERLESS VS PAAS
14. PROJECT STACK
15. CLIENT AUTHENTICATION
16. API-GATEWAY
17. DYNAMODB
18. WHY NOSQL?
19. LAMBDA
20. ASYNC TASKS
21. SNS
22. SYNC TASKS
24. PROBLEMS
25. SERVERLESS FRAMEWORK
26. SERVERLESS.YML
30. DEPLOY
31. DYNAMODB LOCAL
32. SERVERLESS OFFLINE
33. SNS PROBLEM
34. VENDOR LOCK-IN
35. PROJECT USE CASE
36. MVP
37. FEEDBACK LOOP
38. OPTIMIZATION
39. OBSTACLES
40. MANAGE ENVIRONMENTS
41. RESOURCES LIMIT REACHED
42. FIRST SOLUTION
43. ONGOING SOLUTION
44. MICROSERVICES IN SERVERLESS
45. SCALING COSTS
46. OCCASIONAL REQUESTS
47. INCONSISTENT TRAFFIC
48. CONCLUSION
49. THANKS!
50. https://github.com/carolpc https://twitter.com/CarolinaPascale carolina.pascale.c@gmail.com WHERE TO FIND ME