Group 5 Web Engineering Presentation
Group 5 Web Engineering Presentation
Group no. 05
Group Members :
Qura-tul-Ain Saleem 04
Nadia Imtiaz 21
Noor-un-Nisa Sadiq 28
Zainab Yasmin 44
Agenda
1. Introduction to Serverless Architecture
2. How Serverless Works
3. Benefits of Serverless for Web Development
4. Key Components of Serverless Architecture
5. Popular Serverless Platforms
6. Use Cases and Applications
7. Best Practices
8. Case Studies
9. Conclusion and Future Trends
Introduction to Serverless Architecture
What is Serverless Why the Name "Serverless"?
Comparison with
Architecture? Traditional Models
Serverless computing is a • Servers still exist but • Traditional: Developers
cloud computing model where are abstracted away must provision, scale, and
developers only write and from developers. maintain servers.
deploy code, and the cloud • Developers don’t manage • Serverless: Developers
provider manages the or maintain these servers. focus solely on application
underlying infrastructure. logic.
How Serverless Works
Code and Functions
Developers write functions that perform specific tasks.
Event-Driven Model
Functions are triggered by events like API calls, file uploads, or database changes.
Automatic Scaling
Functions scale up or down automatically based on demand.
Key Benefits of Serverless
Reduced Cost Efficiency
Infrastructure
Pay only for execution time.
Management
Developers don’t worry No idle costs when functions
about servers, OS updates, are not in use.
or scaling.
2 Function Execution
The triggered event invokes a corresponding serverless function.
3 Response
The function processes the event and generates a response, which is sent back to the client or
system.
Popular Serverless Platforms
Pay for a fixed capacity, even during low usage periods. Pay only for the resources consumed during code
execution, with no idle costs.
For example, a company was able to save $5,000 per month by switching from virtual machines to a serverless
architecture, paying only for the computing power they used rather than maintaining idle capacity.
Faster Deployments
• Simplified Pipeline: Fewer steps in the deployment process compared to traditional hosting models.
• Rapid Iterations: A travel booking app deploys updates in hours instead of days using a serverless architecture.
• Accelerated Time-to-Market: The simplified deployment pipeline allows for quicker product iterations and
feature releases.
• Reduced Overhead: Serverless deployments eliminate the need for server provisioning and management,
streamlining the process.
Scalability of Serverless
Serverless architectures automatically scale to handle
sudden spikes in workload, making them ideal for
applications that experience unpredictable traffic
patterns.