Serverless - the way microservices should be - OdessaJS

1. Serverless the way microservices should be @ivanjov96
3. How many of you are trying to scale your app?
4. How many DevOps engineers do you have?
5. How many do you really need? 0 Let’s see how
6. Ivan Jovanovic Senior software engineer @ nearForm https://ivanjov.com @ivanjov96
7. How did we get here? Microservices Monolith Serverless ?
8. Monolith
9. Monolith - Pros • Setup • One app to maintain • Deployment • Shared memory between functionalities • Monitoring, logging • Adding new functionalities
10. Monolith - Cons • Extending app without breaking other stuff • Slow delivery and deployments • Large codebase to maintain • Hard to understand • Slower development as it evolves
11. Microservices
12. Microservices - Pros • Service independence • Async communication between services • Independent deployment • Easier to understand, develop and test • Speeds up development • Enables continuous delivery and deployment
13. Microservices - Cons • Setup • Service discovery • Monitoring • Error tracking • Logging
14. How we do microservices now? ➕ ➕
15. Communication
16. How to fix this?
17. Serverless to the rescue!
18. What is serverless?
19. Serverless computing is a cloud- computing execution model in which the cloud provider dynamically manages the allocation of machine resources.
23. Serverless - Pros • Setup, no provision needed • Simplifies packaging and deployment • Cost is small • Reduces the complexity • Automatic scaling
24. Serverless - Cons • Vendor lock in (but doesn’t need be) • No guarantee where will function be executed • Takes some time to handle first request - cold time
25. How does serverless “kill” DevOps? • No need to write any setup code, no containers, orchestration, nothing • Simple deployment • Functions are so small, no space for mistakes • It doesn’t “kill” DevOps, it just takes it to the next level
26. Who are the serverless providers? Amazon Lambda Google Cloud Functions Azure Functions
27. Comparison ⚔ ⚔
28. Comparison ❤ ❤
29. Serverless architecture
31. and more…
32. But it costs
33. And more serverless functions…
34. For free With autoscaling
35. Serverless architecture Synchronous Asynchronous
36. Synchronous
37. Asynchronous
38. Logging AWS CloudWatch
39. Show me the code
43. Tools
44. Claudia.js
47. Claudia API Builder
48. Serverless framework
52. Who is using serveless?
53. Conclusion • Serverless, not just a buzzword • Pick provider and tools that you want • Free autoscaling • Have you infrastructure as a code • Fast development, deployment and delivery
54. Thank you! Blog ivanjov.com Twitter @ivanjov96