1.

Examples of distributed system:

Qualities:
1. Architecture:
 Distributed Systems: Comprise multiple independent nodes that communicate and
coordinate to perform tasks. The nodes can be geographically dispersed and
interconnected via a network.
 Centralized Systems: Consist of a single central node or server that performs all the
processing and stores all the data, with clients or terminals connected to this central
node.
2. Scalability:
 Distributed Systems: Highly scalable. New nodes can be added to the system to handle
increased load or to enhance performance.
 Centralized Systems: Limited scalability. The central server can become a bottleneck as
the load increases, and upgrading it involves significant cost and effort.
3. Fault Tolerance:
 Distributed Systems: More fault-tolerant. Failure of one node does not necessarily bring
down the entire system, as tasks can be redistributed among other nodes.
  Centralized Systems: Less fault-tolerant. If the central node fails, the entire system
becomes inoperable until the issue is resolved.
4. Performance:
 Distributed Systems: Can offer high performance through parallel processing and
resource sharing across multiple nodes.
 Centralized Systems: Performance is constrained by the capacity of the central server.
High load can lead to performance degradation.
5. Resource Management:
 Distributed Systems: Resources (e.g., data storage, processing power) are distributed
across multiple nodes, allowing for efficient resource utilization.
 Centralized Systems: Resources are managed by a single central server, which may lead
to inefficiencies and underutilization during low demand periods.
Advantages:
1. Distributed Systems:
 Scalability: Easy to scale horizontally by adding more nodes.
 Fault Tolerance: High resilience to individual node failures.
 Performance: Potential for improved performance through parallel processing and load
distribution.
 Geographic Distribution: Nodes can be placed in different locations to reduce latency
and improve access speeds for users globally.
2. Centralized Systems:
 Simplicity: Easier to design, implement, and manage due to the centralized architecture.
 Cost Efficiency: Initial setup and maintenance can be cheaper since it involves fewer
components.
 Security: Easier to secure because all data and processing are concentrated in a single
location.
 Consistency: Ensures strong data consistency as all transactions are handled by a single
server.
Complexities:
1. Distributed Systems:
  Complexity: More complex to design, implement, and maintain due to the need for
communication, coordination, and synchronization between nodes.
 Consistency: Achieving data consistency can be challenging (CAP theorem: Consistency,
Availability, Partition tolerance – only two can be fully achieved simultaneously).
 Network Issues: Prone to network-related issues such as latency, bandwidth limitations,
and communication failures.
 Security: More points of vulnerability and potential security breaches due to the
distributed nature of the system.
2. Centralized Systems:
 Single Point of Failure: The central server is a single point of failure, making the entire
system vulnerable to outages.
 Scalability: Limited by the capacity of the central server; scaling up involves significant
costs.
 Performance Bottleneck: The central server can become a bottleneck under high loads,
leading to performance issues.
 Resource Limitation: Limited by the resources (e.g., CPU, memory) of the central server,
which can affect the ability to handle large volumes of data or requests.
Summary:
 Distributed Systems excel in scalability, fault tolerance, and performance through parallelism,
but they come with complexities in design, consistency, and security management.
 Centralized Systems are simpler and more cost-effective to set up and secure, offering strong
consistency and easier management, but they struggle with scalability, fault tolerance, and
performance under high load.