0% found this document useful (0 votes)
4 views16 pages

Lecture 1.1.3

Uploaded by

anujgill240
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views16 pages

Lecture 1.1.3

Uploaded by

anujgill240
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

University Institute of Engineering

DEPARTMENT OF COMPUTER SCIENCE


& ENGINEERING
Bachelor of Engineering (Computer Science & Engineering)
Subject Name: Parallel and Distributed Computing
Subject Code: 22CSH-354/22ITH-354
Prepared by:
Er. Anupama Jamwal (E14665)

Parallel and Distributed Computing DISCOVER . LEARN . EMPOWER

1
Department of Computer Science and Engineering (CSE)

Content

Peer-to-Peer (P2P) Architecture in Distributed Systems


•Advantages, disadvantages
Data-Centic Architecture in Distributed Systems
• Advantages, disadvantages

University Institute of Engineering (UIE) 2


Department of Computer Science and Engineering (CSE)

2. Peer-to-Peer (P2P) Architecture in Distributed Systems


 Peer-to-Peer (P2P) Architecture is a decentralized network
design where each node, or “peer,” acts as both a client and a
server, contributing resources and services to the network. This
architecture contrasts with traditional client-server models,
where nodes have distinct roles as clients or servers.
 In a P2P architecture, all nodes (peers) are equal participants in
the network, each capable of initiating and receiving requests.
 Peers collaborate to share resources, such as files or
computational power, without relying on a central server.

University Institute of Engineering (UIE) 3


Department of Computer Science and Engineering (CSE)

University Institute of Engineering (UIE) 4


Department of Computer Science and Engineering (CSE)

 Key Features of Peer-to-Peer (P2P) Architecture in Distributed Systems


 Decentralization
 Function: There is no central server or authority. Each peer operates independently and
communicates directly with other peers.
 Advantages: Reduces single points of failure and avoids central bottlenecks, enhancing
robustness and fault tolerance.
 Resource Sharing
 Function: Peers share resources such as processing power, storage space, or data with
other peers.
 Advantages: Increases resource availability and utilization across the network.
 Scalability
 Function: The network can scale easily by adding more peers. Each new peer contributes
additional resources and capacity.
 Advantages: The system can handle growth in demand without requiring significant
changes to the underlying infrastructure.

University Institute of Engineering (UIE) 5


Department of Computer Science and Engineering (CSE)

Self-Organization
 Function: Peers organize themselves and manage network
connections dynamically, adapting to changes such as peer arrivals
and departures.
 Advantages: Facilitates network management and resilience without
central coordination.

Advantages of Peer-to-Peer (P2P) Architecture in Distributed Systems


 Fault Tolerance: The decentralized nature ensures that the failure of one or several
peers does not bring down the entire network.
 Cost Efficiency: Eliminates the need for expensive central servers and
infrastructure by leveraging existing resources of the peers.
 Scalability: Easily accommodates a growing number of peers, as each new peer
enhances the network’s capacity.

University Institute of Engineering (UIE) 6


Department of Computer Science and Engineering (CSE)

 Disadvantages of Peer-to-Peer (P2P) Architecture in Distributed


Systems
 Security: Decentralization can make it challenging to enforce security
policies and manage malicious activity, as there is no central authority to
oversee or control the network.
 Performance Variability: The quality of services can vary depending on
the peers’ resources and their availability, leading to inconsistent
performance.
 Complexity: Managing connections, data consistency, and network
coordination without central control can be complex and may require
sophisticated protocols.

University Institute of Engineering (UIE) 7


Department of Computer Science and Engineering (CSE)

Examples of Peer-to-Peer (P2P) Architecture in Distributed Systems


 File Sharing Networks: Systems like BitTorrent allow users to share and
download files from multiple peers, with each peer contributing to the
upload and download processes.
 Decentralized Applications (DApps): Applications that run on
decentralized networks, leveraging P2P architecture for tasks like data
storage and computation.

University Institute of Engineering (UIE) 8


Department of Computer Science and Engineering (CSE)

3. Data-Centic Architecture in Distributed Systems


 Data-Centric Architecture is an architectural style that focuses on the central
management and utilization of data. In this approach, data is treated as a critical
asset, and the system is designed around data management, storage, and retrieval
processes rather than just the application logic or user interfaces.
 The core idea of Data-Centric Architecture is to design systems where data is the
primary concern, and various components or services are organized to support
efficient data management and manipulation.
 Data is centrally managed and accessed by multiple applications or services,
ensuring consistency and coherence across the system.

University Institute of Engineering (UIE) 9


Department of Computer Science and Engineering (CSE)

Key Principles of Data-Centic Architecture in Distributed Systems


 Centralized Data Management:
Function: Data is managed and stored in a central repository or database, making it
accessible to various applications and services.
Principle: Ensures data consistency and integrity by maintaining a single source of
truth.
 Data Abstraction:
Function: Abstracts the data from the application logic, allowing different services or
applications to interact with data through well-defined interfaces.
Principle: Simplifies data access and manipulation while hiding the underlying complexity.
Data Normalization:
Function: Organizes data in a structured manner, often using normalization
techniques to reduce redundancy and improve data integrity.
Principle: Enhances data quality and reduces data anomalies by ensuring consistent
data storage.

University Institute of Engineering (UIE) 10


Department of Computer Science and Engineering (CSE)

University Institute of Engineering (UIE) 11


Department of Computer Science and Engineering (CSE)

Data Integration:
 Function: Integrates data from various sources and systems to provide a
unified view and enable comprehensive data analysis.
 Principle: Supports interoperability and facilitates comprehensive data
analysis across diverse data sources.
Scalability and Performance:
 Function: Designs the data storage and management systems to handle
increasing volumes of data efficiently.
 Principle: Ensures the system can scale to accommodate growing data needs
while maintaining performance.

University Institute of Engineering (UIE) 12


Department of Computer Science and Engineering (CSE)

Advantages:
 Consistency: Centralized data management helps maintain a single source of truth,
ensuring data consistency across the system.
 Integration: Facilitates easy integration of data from various sources, providing a
unified view and enabling better decision-making.
 Data Quality: Data normalization and abstraction help improve data quality and
reduce redundancy, leading to more accurate and reliable information.
 Efficiency: Centralized management can optimize data access and retrieval
processes, improving overall system efficiency.

University Institute of Engineering (UIE) 13


Department of Computer Science and Engineering (CSE)

Disadvantages:
 Single Point of Failure: Centralized data repositories can become a
bottleneck or single point of failure, potentially impacting system reliability.
 Performance Overhead: Managing large volumes of centralized data can
introduce performance overhead, requiring robust infrastructure and
optimization strategies.
 Complexity: Designing and managing a centralized data system can be
complex, especially when dealing with large and diverse datasets.
 Scalability Challenges: Scaling centralized data systems to accommodate
increasing data volumes and access demands can be challenging and may
require significant infrastructure investment.

University Institute of Engineering (UIE) 14


Department of Computer Science and Engineering (CSE)

Examples of Data-Centic Architecture in Distributed Systems


 Relational Databases: Systems like MySQL, PostgreSQL, and Oracle use
Data-Centric Architecture to manage and store structured data efficiently,
providing consistent access and integration across applications.
 Data Warehouses: Platforms such as Amazon Redshift and Google BigQuery
are designed to centralize and analyze large volumes of data from various
sources, enabling complex queries and data analysis.
 Enterprise Resource Planning (ERP) Systems: ERP systems like SAP and
Oracle ERP integrate various business functions (e.g., finance, HR, supply
chain) around a centralized data repository to support enterprise-wide
operations and decision-making.

University Institute of Engineering (UIE) 15


Department of Computer Science and Engineering (CSE)

University Institute of Engineering (UIE) 16

You might also like