AWS: Server Management Simplified
AWS: Server Management Simplified
Cloud Computing means storing and accessing the data and programs on remote
servers that are hosted on the internet instead of the computer’s hard drive or local
server. Cloud computing is also referred to as Internet-based computing, it is a
technology where the resource is provided as a service through the Internet to the
user. The data that is stored can be files, images, documents, or any other storable
document.
The following are some of the Operations that can be performed with Cloud Computing
Storage, backup, and recovery of data
Delivery of software on demand
Development of new applications and services
Streaming videos and audio
Pay Model Pay what you Have a variety of pricing It can include a mix of
used models public cloud pay-as-you-
Factors Public Cloud Private Cloud Hybrid Cloud
The general
Restricted to a specific Can be a combination of
Availability public (over the
organization both.
internet)
Cloud computing offers a range of services that provide scalable and flexible computing
resources over the internet. Here's an overview of the primary services, their benefits,
limitations, and the features of different service models:
Cost Efficiency: Reduces the need for significant upfront hardware investments;
users pay for resources on a subscription or pay-per-use basis.
Scalability: Resources can be quickly scaled up or down based on demand, ensuring
optimal performance during varying workloads.
Accessibility: Enables access to applications and data from any location with an
internet connection, facilitating remote work and collaboration.
Maintenance: Cloud providers handle system updates, security patches, and
maintenance tasks, reducing the workload on internal IT teams.
Limitations of Cloud Computing:
Security and Privacy: Storing data off-premises can raise concerns about
unauthorized access and data breaches.
Downtime: Dependence on internet connectivity means that outages can disrupt
access to services.
Limited Control: Users have less control over the infrastructure and specific
configurations compared to on-premises setups.
Compliance: Ensuring that cloud services meet industry-specific regulatory
requirements can be challenging.
Cloud computing has revolutionized the way organizations and individuals access and
manage computing resources, offering flexibility, scalability, and cost savings. However, it's
essential to consider the associated limitations and choose the appropriate service model
based on specific needs.
Data security in cloud computing
Ensuring data security in cloud computing is paramount, given the increasing reliance on
cloud services for storing and processing sensitive information. Recent developments and
examples highlight both the challenges and advancements in this domain.
1. Client-Side Encryption: This approach involves encrypting data on the user's device
before uploading it to the cloud, ensuring that only authorized users can access the
information. Notable services implementing client-side encryption include:
o Tresorit: A cloud storage service emphasizing end-to-end encryption.
o MEGA: Offers secure cloud storage with user-controlled encryption keys.
o Cryptee: Provides encrypted storage and document editing.
o Cryptomator: Allows users to encrypt files before uploading them to any
cloud service.
Additionally, major providers like Apple and Google have introduced optional client-
side encryption features for services such as iCloud and Google Drive, enhancing user
data protection. citeturn0search10
Cloud providers such as Microsoft Azure, Google Cloud, and IBM Cloud have
integrated confidential computing capabilities into their services, offering enhanced
data security for users. citeturn0search11
These incidents emphasize the critical need for robust security measures in cloud
environments. citeturn0news23
Cloud security services revolve around the CIA triad—Confidentiality, Integrity, and
Availability—ensuring secure and reliable cloud computing. Below is the latest information
on these aspects, including industry trends and recent incidents.
GitHub Source Code Leak (2024): Attackers modified repositories in supply chain
attacks, proving the need for robust integrity checks.
Medibank Data Tampering (2023-24): A ransomware attack led to unauthorized
modifications of medical records, highlighting integrity risks in cloud-stored data.
Google Cloud Global Outage (Feb 2024): A software bug caused downtime for
major clients, impacting enterprise services.
Azure Service Disruptions (2023-24): Frequent power outages and networking
failures affected Microsoft Teams, Outlook, and other services.
1. Confidentiality:
o Use end-to-end encryption and Zero-Trust security.
o Enable multi-factor authentication (MFA).
o Implement Confidential Computing for encrypted data processing.
2. Integrity:
o Deploy blockchain and immutable logs for data audits.
o Use AI-driven anomaly detection to monitor data modifications.
o Implement strong access controls to prevent unauthorized data tampering.
3. Availability:
o Adopt multi-cloud redundancy and disaster recovery plans.
o Use auto-scaling and DDoS mitigation tools.
o Monitor cloud services with real-time threat intelligence.
When developing or deploying secure cloud software, organizations must ensure compliance
with Confidentiality, Integrity, and Availability (CIA) principles, industry standards, and
regulatory requirements. Below are the key functional and non-functional requirements
for secure cloud software.
1. Functional Requirements
These define the specific security features a cloud software solution must have.
Multi-Factor Authentication (MFA): Users must verify identity using at least two
factors (e.g., password + OTP, biometric + security key).
Role-Based Access Control (RBAC): Restricts access based on user roles (admin,
developer, auditor, etc.).
Least Privilege Principle: Users get only the necessary permissions required for
their tasks.
Single Sign-On (SSO): Integration with OAuth 2.0, OpenID Connect, or SAML
for centralized authentication.
End-to-End Encryption (E2EE): Encrypt data before sending it to the cloud; only
authorized users can decrypt it.
Client-Side Encryption: Protects data before uploading it to the cloud (e.g., Google
Drive’s client-side encryption).
Server-Side Encryption (SSE): Cloud providers encrypt stored data with keys
managed by AWS KMS, Azure Key Vault, or Google Cloud KMS.
Secure Data Transmission: Enforce TLS 1.3 for secure network communication.
API Security: Implement OAuth 2.0, API keys, and rate limiting to prevent abuse.
Zero-Trust Architecture: Authenticate every request to cloud resources.
Secure Coding Practices: Use OWASP Top 10 guidelines to avoid vulnerabilities
like SQL injection, XSS, CSRF.
Web Application Firewalls (WAF): Protect applications from web-based attacks.
2. Non-Functional Requirements
GDPR (General Data Protection Regulation) – Ensures data privacy for users in
the EU.
ISO/IEC 27001 – Global cloud security standard ensuring data protection policies.
SOC 2 (Service Organization Control 2) – Certifies cloud providers for security,
availability, and privacy.
HIPAA (Health Insurance Portability and Accountability Act) – Protects medical
data in healthcare cloud applications.
PCI-DSS (Payment Card Industry Data Security Standard) – Ensures secure
online transactions.
A secure cloud software system must integrate strong authentication, data encryption,
real-time monitoring, and compliance with global security standards. By following a Zero-
Trust model and DevSecOps, organizations can ensure highly secure cloud applications
that protect user data, prevent cyber threats, and ensure business continuity.
Secure cloud software testing ensures that cloud applications are protected against security
threats, data breaches, and misconfigurations while maintaining compliance, reliability,
and resilience. Below is a structured approach to secure cloud software testing.
What it does: Combines SAST + DAST, monitoring security flaws in real time.
Tools: HCL AppScan, Contrast Security, Seeker IAST.
Best Practice: Integrate into cloud API security validation.
What it does: Checks for API vulnerabilities like injection attacks, improper
authentication.
Tools: Postman, OWASP API Security Testing, SoapUI.
Best Practice: Enforce OAuth 2.0, API rate limiting, JWT validation.
What it does: Ensures compliance with GDPR, HIPAA, ISO 27001, SOC 2.
Tools: CloudSploit, AWS Artifact, Google Security Command Center.
Best Practice: Automate compliance audits for regulatory tracking.
1️⃣ Plan & Define Security Requirements → (Identify risks & compliance needs).
2️⃣ Perform Static & Dynamic Testing → (Code security, API tests).
3️⃣ Conduct Cloud Penetration Testing → (Simulated attacks on cloud assets).
4️⃣ Monitor & Analyze Security Logs → (SIEM integration for incident response).
5️⃣ Automate & Repeat Testing → (Continuous security validation).
4. Best Practices for Secure Cloud Software Testing
Conclusion
Cloud Analytics
Cloud Analytics refers to the process of analyzing and processing data in the cloud using
scalable computing resources. It enables businesses to collect, store, process, and analyze
large volumes of data without relying on on-premises infrastructure.
Cloud analytics involves multiple components that work together to ingest, store, process,
and analyze data.
The process of collecting and transferring raw data from multiple sources to cloud
storage or processing units.
Sources: IoT devices, logs, transactional systems, social media, CRM, ERP.
Tools: AWS Kinesis, Google Pub/Sub, Azure Event Hubs.
What it does: Recommends actions based on data patterns and AI-driven decision-
making.
Example: Logistics companies use prescriptive analytics to optimize delivery routes
in real-time.
3. Benefits of Cloud Analytics
Amazon Web Services (AWS) AWS Glue, Amazon Redshift, AWS QuickSight
Microsoft Azure Azure Synapse Analytics, Power BI, Azure Data Explorer
🔹 Healthcare
🔹 Financial Services
🔸 Data Privacy Risks: Storing sensitive data in the cloud requires strong encryption and
compliance with regulations like GDPR & HIPAA.
🔸 Data Latency Issues: Real-time analytics may experience lag due to network delays.
🔸 Cost Management: Cloud analytics services can become expensive without proper cost
control strategies.
🔸 Data Governance: Ensuring correct data ownership, classification, and access controls
is critical.
Big Data refers to massive volumes of structured, semi-structured, and unstructured data
generated from various sources, including social media, IoT devices, financial transactions,
and more. Traditional databases fail to handle such large-scale data due to storage and
processing limitations.
Hadoop, an open-source framework, provides a scalable and distributed approach to store and
process big data efficiently. It consists of two main components: HDFS (Hadoop
Distributed File System) for storage and MapReduce for parallel processing. Hadoop's
ecosystem includes tools like Hive, Pig, HBase, and Spark, which enhance data processing,
querying, and real-time analytics. The framework is widely used in industries such as finance,
healthcare, and e-commerce to analyze and extract valuable insights from large datasets.
Computation takes place at the edge of a device’s network, which is known as edge
computing. That means a computer is connected with the network of the device, which
processes the data and sends the data to the cloud in real-time. That computer is
known as “edge computer” or “edge node”.
With the rise of IoT and real-time applications, traditional cloud computing faces
latency and bandwidth constraints. Edge computing solves this by processing data closer
to the source (i.e., at edge devices like sensors, routers, and gateways), reducing
response time and dependency on centralized cloud servers. It is commonly used in
applications like autonomous vehicles, smart cities, and industrial automation.
Autonomous vehicle edge computing devices collect data from cameras and sensors
on the vehicle, process it, and make decisions in milliseconds, such as self-parking
cars.
Fog computing, on the other hand, acts as an intermediary layer between edge devices and
the cloud, extending cloud capabilities closer to the data source. It enables pre-processing,
filtering, and analytics before sending data to the cloud, thereby improving efficiency and
security. While edge computing focuses on local processing, fog computing ensures a
distributed and hierarchical approach, balancing cloud and edge resources. Together, these
paradigms enhance the performance of IoT ecosystems, ensuring low-latency and scalable
solutions for real-time applications.
The devices comprising the fog infrastructure are known as fog nodes.
In fog computing, all the storage capabilities, computation capabilities, data along with
the applications are placed between the cloud and the physical host.
All these functionalities are placed more towards the host. This makes processing faster
as it is done almost at the place where data is created.
It improves the efficiency of the system and is also used to ensure increased security.
History of Fog Computing
The term fog computing was coined by Cisco in January 2014. This was because fog is
referred to as clouds that are close to the ground in the same way fog computing was related
to the nodes which are present near the nodes somewhere in between the host and the cloud.
It was intended to bring the computational capabilities of the system close to the host
machine. After this gained a little popularity, IBM, in 2015, coined a similar term
called “Edge Computing”.
Types of Fog Computing
Device-level Fog Computing: Device-level fog computing utilizes low-power
technology, including sensors, switches, and routers. It can be used to collect data from
these devices and upload it to the cloud for analysis.
Edge-level Fog Computing: Edge-level fog computing utilizes network-connected
servers or appliances. These devices can be used to process data before it is uploaded to
the cloud.
Gateway-level Fog Computing: Fog computing at the gateway level uses devices to
connect the edge to the cloud. These devices can be used to control traffic and send only
relevant data to the cloud.
Cloud-level Fog Computing: Cloud-level fog computing uses cloud-based servers or
appliances. These devices can be used to process data before it is sent to end users.
Components of Fog Computing
Edge devices: Edge devices are the network devices nearest to the data source. Edge
devices consist of sensors, PLCs (programmable logic controllers), and gateway routers.
Data Processing: Data processing occurs locally on edge devices rather than being
routed to a central location for processing. The end effect is greater performance and
lower latency.
Data Storage: in Data storage. Instead of transferring data to a central place, edge
devices can keep information locally. This increases security and privacy while
lowering latency.
Connectivity: For fog computing to work, edge devices must be connected to the rest
of the network at high speeds. This can be done using wired or wireless methods.
When to Use Fog Computing?
It is used when only selected data is required to send to the cloud. This selected data is
chosen for long-term storage and is less frequently accessed by the host.
It is used when the data should be analyzed within a fraction of seconds i.e Latency
should be low.
It is used whenever a large number of services need to be provided over a large area at
different geographical locations.
Devices that are subjected to rigorous computations and processings must use fog
computing.
Real-world examples where fog computing is used are in IoT devices Devices with
Sensors, Cameras (IIoT-Industrial Internet of Things), etc.
Advantages of Fog Computing
This approach reduces the amount of data that needs to be sent to the cloud.
Since the distance to be traveled by the data is reduced, it results in saving network
bandwidth.
Reduces the response time of the system.
It improves the overall security of the system as the data resides close to the host.
It provides better privacy as industries can perform analysis on their data locally.
Disadvantages of Fog Computing
Congestion may occur between the host and the fog node due to increased traffic (heavy
data flow).
Power consumption increases when another layer is placed between the host and the
cloud.
Scheduling tasks between host and fog nodes along with fog nodes and the cloud is
difficult.
Data management becomes tedious as along with the data stored and computed, the
transmission of data involves encryption-decryption too which in turn release data.
Applications of Fog Computing
It can be used to monitor and analyze the patients’ condition. In case of emergency,
doctors can be alerted.
It can be used for real-time rail monitoring as for high-speed trains we want as little
latency as possible.
It can be used for gas and oils pipeline optimization. It generates a huge amount of data
and it is inefficient to store all data into the cloud for analysis.
Difference Between Edge Computing and Fog Computing
Edge Computing Fog Computing
Nodes are installed far away from Nodes in this computing are installed closer to
the cloud. the cloud(remote database where data is stored).
Edge computing helps devices to get Fog computing helps in filtering important
faster results by processing the data information from the massive amount of data
simultaneously received from the collected from the device and saves it in the
devices. cloud by sending the filtered data.
Fog computing is an extension of cloud computing. It is a layer in between the edge and the
cloud. When edge computers send huge amounts of data to the cloud, fog nodes receive the
data and analyze what’s important. Then the fog nodes transfer the important data to the
cloud to be stored and delete the unimportant data or keep them with themselves for further
analysis. In this way, fog computing saves a lot of space in the cloud and transfers
important data quickly.
Difference Between Edge Computing and Fog Computing
[Link]. EDGE COMPUTING FOG COMPUTING
Graphics Processing Units (GPUs) are designed for high-throughput, massively parallel
computations. Unlike CPUs, which optimize for sequential processing, GPUs leverage
thousands of cores to execute multiple tasks simultaneously. NVIDIA CUDA (Compute
Unified Device Architecture) is a parallel computing platform and API that enables
developers to use NVIDIA GPUs for general-purpose computing (GPGPU).
Deep Learning & AI: CUDA powers frameworks like TensorFlow and PyTorch,
enabling fast training of deep neural networks.
Scientific Simulations: Used in physics, bioinformatics, and climate modeling for
high-speed calculations.
Cryptography & Blockchain: GPU-based acceleration enhances encryption and
blockchain mining efficiency.
Computer Vision & Image Processing: CUDA accelerates real-time object
detection and video analytics.
Custom-designed chips for dedicated tasks, such as Bitcoin mining (Bitmain's ASIC
miners) and AI acceleration (TPUs, Habana Gaudi, and Graphcore IPUs).
d) Neuromorphic Chips
Conclusion
Parallelism in GPUs (via CUDA) enables massive acceleration in AI, gaming, and scientific
computations. Hardware accelerators like TPUs, FPGAs, and ASICs offer domain-specific
speedups, making modern computing more efficient. The integration of these parallel
architectures continues to push the boundaries of high-performance computing.
Apache Spark
Apache Spark is an open-source, fast, distributed computing framework used for big
data processing. It was developed at UC Berkeley and is now maintained by the Apache
Software Foundation.
It allows you to write applications that process large-scale data quickly by spreading the
work across multiple computers (nodes) and performing computations in memory (RAM),
which makes it faster than traditional systems like Hadoop MapReduce.
Features of Apache Spark
1. In-Memory Computation
o Spark processes data in memory instead of writing to disk at each step like
Hadoop.
o This makes Spark up to 100x faster in some cases.
2. Supports Multiple Languages
o You can write Spark programs in Python, Java, Scala, R, and SQL.
3. Unified Framework
o Spark supports:
Batch Processing
Streaming Data Processing
Machine Learning (MLlib)
Graph Processing (GraphX)
SQL Queries (Spark SQL)
4. Distributed Processing
o Spark can run on clusters (groups of connected machines), allowing parallel
processing of big datasets.
Driver Program:
The main program that defines the Spark job and sends tasks to executors.
Cluster Manager:
Manages resources across the cluster (e.g., YARN, Mesos, or Spark’s own standalone
manager).
Executors:
Workers that run the actual tasks and return the results to the driver.
Resilient Distributed Datasets (RDD):
Immutable, distributed collections of objects. RDDs are the building blocks of Spark.
Spark Workflow
2. Machine Learning:
3. Recommendation Systems:
4. Log Analysis:
Google Inc. developed the Google File System (GFS), a scalable distributed file system
(DFS), to meet the company’s growing data processing needs. GFS offers fault tolerance,
dependability, scalability, availability, and performance to big networks and connected nodes.
GFS is made up of a number of storage systems constructed from inexpensive commodity
hardware parts. The search engine, which creates enormous volumes of data that must be
kept, is only one example of how it is customized to meet Google’s various data use and
storage requirements.
The Google File System reduced hardware flaws while gains of commercially available
servers.
GoogleFS is another name for GFS. It manages two types of data namely File metadata and
File Data.
The GFS node cluster consists of a single master and several chunk servers that various client
systems regularly access. On local discs, chunk servers keep data in the form of Linux files.
Large (64 MB) pieces of the stored data are split up and replicated at least three times around
the network. Reduced network overhead results from the greater chunk size.
Without hindering applications, GFS is made to meet Google’s huge cluster requirements.
Hierarchical directories with path names are used to store files. The master is in charge of
managing metadata, including namespace, access control, and mapping data. The master
communicates with each chunk server by timed heartbeat messages and keeps track of its
status updates.
More than 1,000 nodes with 300 TB of disc storage capacity make up the largest GFS
clusters. This is available for constant access by hundreds of clients.
Components of GFS
A group of computers makes up GFS. A cluster is just a group of connected computers. There
could be hundreds or even thousands of computers in each cluster. There are three basic
entities included in any GFS cluster as follows:
GFS Clients: They can be computer programs or applications which may be used to
request files. Requests may be made to access and modify already-existing files or add
new files to the system.
GFS Master Server: It serves as the cluster’s coordinator. It preserves a record of the
cluster’s actions in an operation log. Additionally, it keeps track of the data that describes
chunks, or metadata. The chunks’ place in the overall file and which files they belong to
are indicated by the metadata to the master server.
GFS Chunk Servers: They are the GFS’s workhorses. They keep 64 MB-sized file
chunks. The master server does not receive any chunks from the chunk servers. Instead,
they directly deliver the client the desired chunks. The GFS makes numerous copies of
each chunk and stores them on various chunk servers in order to assure stability; the
default is three copies. Every replica is referred to as one.
Features of GFS
Namespace management and locking.
Fault tolerance.
Reduced client and master interaction because of large chunk server size.
High availability.
Critical data replication.
Automatic and efficient data recovery.
High aggregate throughput.
Advantages of GFS
1. High accessibility Data is still accessible even if a few nodes fail. (replication)
Component failures are more common than not, as the saying goes.
2. Excessive throughput. many nodes operating concurrently.
3. Dependable storing. Data that has been corrupted can be found and duplicated.
Disadvantages of GFS
1. Not the best fit for small files.
2. Master may act as a bottleneck.
3. unable to type at random.
4. Suitable for procedures or data that are written once and only read (appended) later.
Google File System (GFS) is a proprietary distributed file system developed by Google to
meet the demands of storing and managing large-scale data across many machines. It is a
core part of parallel and distributed computing frameworks because it enables scalable, fault-
tolerant, and high-throughput data access over clusters of commodity hardware.
1. Master-Slave Architecture:
o Master Node: Manages metadata (filenames, directories, and chunk
locations).
o Chunkservers: Store actual data in fixed-size chunks (typically 64MB).
o Each file is split into chunks and replicated across multiple chunkservers for
fault tolerance.
2. Parallelism:
o Clients can read/write chunks directly from multiple chunkservers in parallel.
o Improves speed and efficiency — vital for tasks like indexing the web or
processing large-scale logs.
3. Fault Tolerance:
o Automatic detection and re-replication of failed chunks.
o Ensures data reliability in the presence of hardware failures.
Massive video files are split into chunks and stored redundantly.
Playback and processing (like recommendation generation) are done via distributed
reads.
Emails, attachments, and metadata are stored and accessed using distributed storage.
GFS revolutionized how large-scale systems store and process data by providing a scalable,
parallel, and distributed file system that ensures high availability and performance. Its
architecture inspired systems like HDFS (Hadoop Distributed File System) and remains a
backbone for many real-time, cloud-scale services we use daily.
Sure! Here’s a detailed explanation of MapReduce along with a real-life example to make it
easier to understand:
🔷 What is MapReduce?
1. Map: Breaks down tasks and applies a function to each piece of data.
2. Reduce: Aggregates the results of the Map phase to give final output.
🔶 Working Mechanism
🔸 1. Map Phase
Output from the Map phase is shuffled so that values with the same key are grouped
together.
🔸 3. Reduce Phase
A reducer function aggregates values with the same key to produce the final result.
Problem: Count how many times each word appears in a large collection of documents.
🟢 Map Phase:
Each line in each document is split into words. For every word, it emits a key-value pair:
Suppose Amazon wants to calculate total sales per product from millions of sales records.
Map Step: Extract product and amount from each record → (product_id, amount)
Shuffle: Group all amounts by product ID.
Reduce Step: Sum the sales for each product ID.
✅ Benefits of MapReduce
Edge computing processes data on local devices like sensors, reducing latency and dependency on cloud connectivity. In contrast, fog computing introduces an intermediary layer between edge devices and the cloud, which helps perform preprocessing and analytics locally. This distributed method improves efficiency and security .
FaaS is highly beneficial in scenarios where demand fluctuates or where tasks are triggered by specific events, as it automatically scales and charges based on compute time used. This model reduces costs by not requiring dedicated servers and offers faster development times, especially suitable for services like image processing in e-commerce platforms .
A company might choose fog computing over edge computing due to its ability to provide a distributed and hierarchical approach that balances cloud and edge resources. Fog computing allows for preprocessing and analytics closer to the source, improving system efficiency and response times. It is particularly useful when different geographical locations require real-time services or high scalability .
Businesses using public cloud services may face challenges in ensuring compliance with specific regulatory standards pertaining to data privacy and security. The use of third-party infrastructure can complicate adherence to requirements like GDPR or CCPA, and understanding the data handling practices of cloud providers is critical to maintaining regulatory compliance .
The public cloud model offers cost efficiency because users pay only for the resources they use, eliminating the need for significant upfront investments in physical infrastructure. Furthermore, it provides automatic software updates, which reduce the burden of manual management, and global accessibility through any internet connection .
Real-time data processing in edge computing significantly impacts industries by reducing latency and enabling immediate decision-making. In autonomous vehicles, it allows for quick processing of data from cameras and sensors, essential for dynamic functions like self-parking. In healthcare, it assists in real-time monitoring and assessment of patient data, which can prompt immediate interventions .
IaaS provides virtualized computing resources with substantial flexibility and control over operating systems and applications, but it requires users to manage these resources themselves. PaaS offers development platforms with tools and components, concentrating on application development rather than underlying infrastructure management, thus providing less control but greater ease of use and integrated scalability .
Public clouds pose a higher risk of data breaches and unauthorized access as data is stored on third-party servers, leading to potential vulnerabilities. In contrast, private clouds offer enhanced security and privacy as they are owned and controlled by a single organization, allowing for custom security protocols tailored to specific needs .
Client-side encryption enhances data security by encrypting data on a user's device before it is uploaded to the cloud. This ensures that only authorized users with the decryption keys can access the information, significantly reducing the risk of unauthorized data access .
The operational cost of fog computing is generally lower than traditional cloud computing because it reduces the amount of data sent to the cloud, thereby saving on bandwidth costs. It also locates processing near data sources, which can cut down on latency-related expenses. However, it may incur additional costs related to power consumption and complex task scheduling .