Section 15.136 Serverless Flashcards
Objective 3.1 Compare and contrast security implications of different architecture models. Objectives 4.1 Given a scenario, apply common security techniques to computing resources
Severless
Serverless computing doesn’t mean no servers; it shifts server
■ Relies on cloud service providers to handle server management, databases, and some application logicmanagement away from developers
AWS Lambda
Google Cloud Functions
Functions as a Service (FaaS) Model: Developers write and deploy individual functions triggered by events. This is different from the traditional service based model where applications run continuously regardless of demand.
Benefits of Serverless
Reduced operational costs
Pay only for compute time used, no charges when code is idle
Benefits of Serverless
Automatic scaling
Cloud provider scales resources based on workload, ensuring optimal
capacity
Applications always at the right capacity
Benefits of Serverless
Focus on core product
Developers can concentrate on application functionality, not server management
Benefits of Serverless
Faster time to market
Reduced infrastructure concerns speed up application development
Serverless Challenges and Risks
Vendor Lock-in
Reliance on proprietary interfaces limits flexibility and may increase costs
Makes it challenging to switch providers or use multiple providers
Serverless Challenges and Risks
Immaturity of best practices
Serverless is a relatively new field, and best practices are still evolving
