"Node.js and Serverless" Viacheslav Panevskyi
0 likes876 views
The document provides an overview of serverless architecture, specifically focusing on Node.js and Function-as-a-Service (FaaS) concepts. It outlines the pros and cons of serverless computing, including benefits like cost-effectiveness and scalability, as well as drawbacks such as vendor lock-in and cold start issues. Additionally, it discusses best practices and resources for implementing serverless solutions in production environments.
"Node.js and Serverless" Viacheslav Panevskyi
- 2. Viacheslav Panevskyi Node.js Tech lead at Yalantis 10 years of production experience Area of interests: ‣ software architectures / engineering ‣ travelling ‣ psychology AGENDA ABOUT ME
- 3. AGENDA GOALS ▸ What is Serverless and FaaS ? ▸ What are pros and cons of that approach? ▸ When do we have to choose Serverless? ▸ NodeJS use cases?
- 4. WHAT IS SERVERLESS? SOFTWARE SYSTEM EVOLUTION
- 5. WHAT IS SERVERLESS? ARCHITECTURE / TECHNOLOGY
- 7. WHAT IF?
- 10. COMMON LAMBDA USE CASES
- 11. SERVERLESS INCLUDES DIFFERENT CATEGORIES OF SERVICES
- 15. SERVERLESS FRAMEWORK OVERVIEW SERVERLESS CLI COMMANDS
- 16. SERVERLESS OVERVIEW ANATOMY OF LAMBDA FUNCTION
- 18. SERVERLESS EXAMPLE CONVERTING AN EXISTING EXPRESS APPLICATION
- 20. SERVERLESS PROS AND CONS PROS OF SERVERLESS COMPUTING ▸ Cheaper than the traditional cloud ▸ Scalable & HA - Amazon, Microsoft and Google are better at scaling than anything you can hire ▸ Management of infrastructure - Buying and configuring servers is costly in terms of initial investment and specialized staff required ▸ Easy deployment - developers don’t have to wait for OPS, DBA, etc, no need to worry about Linux, Docker updates ▸ Ability to focus on user experience and business logic
- 21. SERVERLESS PROS AND CONS CONS OF SERVERLESS COMPUTING ▸ Vendor lock-in ▸ Learning curve ▸ Unsuitable for long term tasks (API Gateway has a timeout of 30 seconds, and Lambda has a maximum execution time of 5 minutes) ▸ For apps that may not see traffic for several minutes at a time, you could see cold starts ▸ Cannot use native libraries (aka Addons) unless you package your app on an EC2 machine running Amazon Linux
- 22. LAMBDA LIMITATION COLD STARTS ▸ What is a Cold Start? ▸ When does a Cold Start occur?
- 23. SERVERLESS ARCHITECTURE LEVEL OF COMPLEXITY
- 25. BEST PRACTICE SMART RESOURCE ALLOCATION
- 26. SERVERLESS USAGE IN PRODUCTION CASE STUDIES
- 28. SERVERLESS ARCHITECTURE MICROSERVICES AND SERVERLESS
- 29. SERVERLESS ARCHITECTURE LAMDAS AS MICRO-SERVICES ▸ Events are first-class citizens ▸ Every lambda scales independently ▸ Agility (develop feature quick and in an isolated fashion) ▸ Language-agnostic Classic micro-services concerns: ▸ Granularity (how to separate features? BDD? Bounded context?) ▸ Orchestration (dependencies between lambdas, service discovery)
- 30. BEST PRACTICE THE 12 FACTOR PRINCIPLES
- 31. BEST PRACTICE THE 12 FACTOR PRINCIPLES AND SERVERLESS
- 32. BEST PRACTICE