seminardocumentation
seminardocumentation
SEMINAR Report
On
SERVERLESS COMPUTING
In partial fulfillment for the award of the degree
Of
[B.C.A]
Year 2025-2026
SUBMITTED BY: GUIDED
BY:
BCA-6 th SEMESTER
Submitted to:
Affiliated to
ACKNOWLEDGEMENT
SERVERLESS COMPUTING
I would like to express our gratitude to all the people behind the screen who
helped us to transform an idea a real application. I would like to express our
heartfelt gratitude to my parents without whom we would not have been
privileged to achieve and fulfill my dream.Anahita Pithawala our professor and
seminar guide hasbeen an enormous source Of blessing, inspiration, motivation &
and great encouragement about seminarwork. The satisfaction and euphoria that
accompany the successful completion of the task would be great but incomplete
without the mention of the people who made it possible with their constant
guidance andencouragement crowns all the efforts with success. In this context, I
would like to thank all the other staffmembers, both teaching and non-teaching ,
who have extended their timely help and eased our task.
From,
Reni kukadiya
SERVERLESS COMPUTING
Contents(index) II
Abstract III
1 History 1
2 Introduction
6 Diagrams or figures
10 Conclusion
11 References
Abstract:-
SERVERLESS COMPUTING
2008 Google App Engine Google introduced its first PaaS offering, enabling
Launched automatic scaling and management of web
applications.
2016 Microsoft Azure Functions Microsoft and IBM entered the serverless market
& IBM OpenWhisk with Azure Functions and IBM OpenWhisk
Launched (now IBM Cloud Functions).
2017 Google Cloud Functions Google joined the serverless computing trend by
Introduced launching Google Cloud Functions as an event-
driven FaaS solution.
AWS introduced Fargate, a serverless computing
2018 AWS Fargate Introduced service for running containers without managing
servers.
Introduction:-
what is Serverless computing:-
Serverless computing is a modern cloud computing model that allows developers to build and
deploy applications without managing the underlying infrastructure. In this model, cloud
providers automatically handle server provisioning, scaling, and maintenance, enabling
developers to focus entirely on writing code.
Serverless computing is a revolutionary shift in cloud computing that eliminates the need for
developers to manage and maintain servers. Unlike traditional architectures, where applications
SERVERLESS COMPUTING
Serverless computing is a cloud execution model where developers build and deploy applications
without managing servers. Cloud providers handle provisioning, scaling, and maintenance,
allowing developers to focus solely on writing code.
Key Features:
Components:
Benefits:
Challenges:
Use Cases:
Conclusion:
Serverless computing simplifies deployment, enhances scalability, and optimizes costs, making it
a game-changer for modern cloud-based applications.
SERVERLESS COMPUTING
Example:
A network of IoT sensors continuously collects temperature data and sends it to a serverless
function for analysis.
1.IoT Devices Collect Data → Sensors measure temperature, motion, or any other information.
2.Data is Sent to the Cloud → The device sends this data to a cloud service like AWS IoT Core
or Google Cloud IoT.
3.A Serverless Function Processes the Data → A function (like AWS Lambda or Google
Cloud Functions) cleans, filters, and analyzes the data.
4.Data is Stored in a Database → The processed data is saved in a database like DynamoDB or
Firebase Firestore.
Notifications & Actions are Triggered → If an issue is detected (e.g., high temperature), an alert is sent
via email, SMS, or an app.
SERVERLESS COMPUTING
A web application backend is like the brain of a website. It handles user requests, processes
data, and sends responses without the user seeing how it works.
2.API Gateway Receives the Request → Think of this as a receptionist that directs the request to the
right place.
3.Serverless Function Processes the Request → A function (like AWS Lambda) runs only when needed,
handling things like data validation or calculations.
4.Data is Stored in a Database → If needed, the function saves or retrieves data from a cloud database
(like DynamoDB).
5.Response is Sent Back to the User → The processed data is sent back, and the website updates
accordingly.
SERVERLESS COMPUTING
Example:
A user interacts with a chatbot, and the backend logic is handled through serverless functions.
✅ Workflow:
Uses:
Example:
A website allows users to upload profile pictures, which are automatically resized and optimized
using serverless computing.
✅ Workflow:
SERVERLESS COMPUTING
Uses:
Example:
A business receives daily log files, which need to be processed in real-time.
✅ Workflow:
Uses:
Applications :-
As you may have gleaned from the examples, serverless computing can be
applied in various ways. It drives efficient resource allocation, supports high
bandwidth scalability, and delivers dynamic data updates. Here are the four
primary applications of serverless:
the week and seasons of the year. A serverless architecture means you can
quickly scale to cater to a demand uptick and increase your profitability
without having those resources lie idle 24/7/365. Similarly, on-demand
learning content providers, webinar hosts, etc., can also gain from
serverless.
Serverless computing is a cloud-native execution model where cloud providers dynamically manage
infrastructure, allowing developers to run functions without provisioning or maintaining servers. The
provided diagram illustrates how serverless computing architecture works, showing how different
components interact to process events and execute functions efficiently.
This section is responsible for capturing user requests or events and forwarding them for
processing.
🔹 UI (User Interface)
🔹 API Gateway
A critical component that acts as a middle layer between the client (user) and serverless
functions.
It validates requests, ensures security, and directs them to the appropriate service.
Example: If a user requests to view product details, the API Gateway sends this request to a
function that fetches product data.
SERVERLESS COMPUTING
Events can come from different cloud sources like databases, IoT devices, file uploads, or third-
party services.
Example: A new file upload to cloud storage triggers a function to process the file and store
metadata.
The event queue temporarily holds all incoming requests before sending them for execution.
It ensures that requests are processed in an orderly manner and prevents system overload.
Example: If 1,000 users request data at the same time, the queue manages them efficiently.
The dispatcher picks events from the queue and forwards them to an available worker node
(serverless function) for execution.
It ensures load balancing by distributing work efficiently.
These are stateless functions that execute a specific piece of code when triggered.
Each worker node runs independently and scales automatically.
Workers can scale up and down based on demand.
Example: During high traffic, more worker nodes activate; during low traffic, fewer are
active.
SERVERLESS COMPUTING
After the worker function executes the request, it sends the result back to the user through the
API Gateway.
Example: If a user requested weather data, the function fetches the latest temperature and
returns it.
Cloud providers track performance, errors, and security logs to ensure smooth operation.
Example: AWS CloudWatch, Azure Monitor, or Google Stackdriver.
Advantages:-
1.Cost Efficiency
You only pay for actual execution time instead of maintaining always-on
infrastructure.
Eliminates costs related to provisioning and managing servers.
2.Auto Scaling
4.Reduced Maintenance
7.Environmentally Friendly
SERVERLESS COMPUTING
Disadvantages:-
1. Cold Start Issues
The first invocation of a function can have increased latency due to initialization time.
May affect performance for latency-sensitive applications.
Serverless functions have execution time limits (e.g., AWS Lambda has a maximum limit
of 15 minutes).
Not suitable for long-running processes.
3 Vendor Lock-in
Developers have minimal control over hardware, networking, and operating system
configurations.
Troubleshooting performance issues can be difficult.
5. Security Concerns
Traditional debugging tools may not work efficiently with serverless applications.
Logs and monitoring need to be integrated with cloud-based services for visibility.
Serverless computing eliminates the need for managing infrastructure, allowing developers to
focus entirely on writing and deploying code. The cloud provider automatically manages scaling,
resource allocation, and execution.
Key Features:
Use Cases:
2. Containers
Containers package an application and its dependencies together, ensuring that it runs
consistently across different computing environments. Containers use platforms like Docker and
Kubernetes for orchestration.
Key Features:
Use Cases:
Microservices architecture.
Running legacy applications in a modern environment.
Hybrid cloud and multi-cloud deployments.
PaaS provides a cloud-based platform where developers can build, run, and manage applications
without worrying about the underlying infrastructure. It offers services like databases, runtime
environments, and development tools.
Key Features:
Use Cases:
IaaS offers virtualized computing resources over the internet. Users can create and manage
virtual machines, storage, and networking. It provides the most flexibility but requires significant
management.
Key Features:
Use Cases:
Comparison Summary
Serverless (FaaS): Best for event-driven, highly scalable applications with minimal management.
Containers: Offers portability and consistency, suitable for microservices and hybrid
deployments.
PaaS: Simplifies development but has platform limitations. Best for web and enterprise apps.
IaaS: Provides full control but requires manual management, best for large-scale applications.
One major challenge of serverless computing is the "cold start" issue, where a function takes
time to initialize when invoked after being idle. Future improvements may include:
Pre-warmed instances: Cloud providers will optimize function execution by keeping instances
warm.
Smarter scheduling: AI-driven workload predictions will reduce latency.
Edge computing integration: Deploying serverless functions closer to the user to minimize
delays.
Impact: Faster response times and improved performance for real-time applications.
Security is a primary concern in serverless environments. Future advancements will focus on:
Better function isolation: Using technologies like sandboxing to ensure greater security.
Zero-trust security models: Implementing authentication at every layer to prevent unauthorized
access.
Automated compliance monitoring: Cloud providers will offer built-in compliance solutions for
industries like healthcare and finance.
Impact: Enhanced security, making serverless suitable for handling sensitive data.
Currently, serverless platforms charge based on execution time and resources used. Future billing
enhancements may include:
Auto-scaling ML inference models: Run AI models only when needed, reducing costs.
Serverless data pipelines: Automate AI-driven analytics without managing infrastructure.
Edge AI: Deploying AI models on edge devices for real-time processing.
Currently, serverless solutions are often tied to a single cloud provider (AWS Lambda, Azure
Functions, Google Cloud Functions). Future improvements include:
Cross-cloud serverless functions: Ability to run functions across multiple cloud providers.
On-premises serverless: Running serverless applications on private data centers.
Seamless cloud migration tools: Easier transitions between different cloud platforms.
Today, serverless is mainly suited for stateless applications. Future advancements will include:
Longer function execution times: Allowing functions to run continuously for extended periods.
Built-in state management: Supporting in-memory data persistence within serverless functions.
Serverless databases: Enhancing database connectivity for real-time processing.
Impact: Expansion of serverless computing to more complex workloads like gaming, IoT, and
financial applications.
Large enterprises are still hesitant to fully embrace serverless due to security and performance
concerns. Future improvements will address:
Serverless DevOps: More automation tools for CI/CD integration in serverless workflows.
Impact: Increased enterprise adoption and seamless integration with existing IT infrastructure.
Despite its many advantages, serverless computing is not a one-size-fits-all solution. It excels in
scenarios requiring event-driven workflows, microservices, API backends, and IoT
applications. However, challenges such as cold start delays, vendor lock-in, and limited
execution time still need to be addressed for broader adoption.