Summary of "Lec 5: Distributed Computing Paradigms"

Overview

Core principle: split a big problem into smaller tasks, run them on multiple machines, and combine results.

This lecture surveys several distributed computing paradigms that evolved to address the limits of the classic client–server model. Each paradigm is described with its definition, key properties, pros/cons, and examples.

Paradigms covered

Peer-to-Peer (P2P)

• Definition: Symmetric, decentralized architecture where each node (peer) can act as both client and server.
• Key properties:
  • No central server
  • Resource-sharing among peers
  • High scalability
  • No single point of failure
• Downsides:
  • Security and trust issues (malicious peers)
  • Availability and management complexity
  • Hard to roll out updates across all peers
• Examples / use cases:
  • Blockchain networks
  • File/document sharing between neighbors (analogy)

Cluster Computing

• Definition: Group of tightly-coupled, co-located independent machines (nodes) connected by a high-speed network that act like one powerful machine.
• Key properties:
  • Tightly coupled
  • Low-latency LAN connectivity
  • Appears as a single system to users
• Goals: Improve performance, scalability, and reliability for compute-intensive tasks.
• Examples:
  • High-performance computing (HPC) clusters
  • Hadoop clusters for big data analytics

Grid Computing

• Definition: Loosely-coupled, geographically distributed collection of heterogeneous resources (across organizations) working under common protocols to form a “virtual supercomputer.”
• Key properties:
  • Resource sharing across institutions
  • Tasks distributed to remote sites
  • Loosely coupled
• Goals: Solve very large or high-compute problems by borrowing cycles from many organizations.
• Examples:
  • SETI-style volunteer computing
  • Cross-institution compute collaborations

Utility Computing

• Definition: Renting compute resources on a pay-per-use / metered basis (the conceptual precursor to public cloud).
• Key properties:
  • No upfront investment
  • Pay only for consumption
  • Scalable renting of hardware/software
• Goal: Cost efficiency and elastic resource usage.
• Relation: Core idea behind modern cloud offerings.

Cloud Computing

• Definition: Delivery of on-demand computing services over the Internet on a pay-as-you-go basis.
• Key properties:
  • On-demand self-service
  • Elastic scaling
  • Global access
  • Managed backups and services
• Advantages:
  • Auto-scaling during spikes
  • Global availability
  • Reduced operational overhead
• Examples: AWS, Azure, Google Cloud

Edge Computing

• Definition: Move computation close to data sources (IoT devices) to reduce latency and bandwidth use.
• Key properties:
  • Local processing at or near sensors/devices (edge nodes)
  • Low latency
  • Reduced need to send raw data to the cloud
• Use cases:
  • IoT scenarios such as agriculture sensors, traffic signals, and appliances where fast local response is required

Fog Computing (Fogging)

• Definition: Intermediate layer between cloud and edge — distributed mini-data-centers (fog nodes) that aggregate and pre-process local data before sending it to the cloud.
• Key properties:
  • Regional aggregation
  • Lower latency than cloud-only approaches
  • Selective offload of heavier tasks to the cloud
• Role: Balance between edge locality and centralized cloud capabilities

Other notes

• Serverless computing was mentioned as a trending cloud variant (not deeply covered in this lecture); it is considered a related/distributed approach to be covered later.
• The lecture used an extended “city of data / grand festival” analogy to illustrate trade-offs between centralized and distributed architectures:

  Neighbors help = P2P; central operations = cluster; borrow from other cities = grid; rent power = utility/cloud; local device processing = edge; fog = intermediate mini-clouds.

Topics covered (tutorial/guide list)

• Recap: Client–server
• Peer-to-peer (P2P): concept, trade-offs, blockchain example
• Cluster computing: architecture, Hadoop example
• Grid computing: cross-organization resource sharing, SETI-style example
• Utility computing → Cloud computing: pay-per-use, AWS/Azure/GCP
• Edge computing: IoT-focused low-latency processing
• Fog computing: fog nodes between edge and cloud
• Mention: Serverless computing (upcoming)

Examples / Technologies mentioned

• Blockchain
• Hadoop
• SETI / volunteer computing
• AWS, Azure, Google Cloud
• IoT devices / sensors

Main speaker / source

Course lecturer (unnamed) — university / online lecture-style instructor using the “city of data” analogy.

Category

Technology

---

Share this summary

Share on X/Twitter Share on Facebook Share on LinkedIn Share on Reddit Share on WhatsApp Share on Telegram

---

Is the summary off?

If you think the summary is inaccurate, you can reprocess it with the latest model.

Reprocess summary

Video