Scribd
Upload
8 views3 pages

Distributed System Design

Uploaded by

Omaisa Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
8 views3 pages

Distributed System Design

Uploaded by

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

Distributed System Design

This slide introduces the different models used to describe the properties and
design issues of distributed systems. Here's a detailed breakdown:

Physical Models:
These models explain the system in terms of hardware, like computers, other
devices (phones, tablets), and the networks connecting them.
It's about how the devices are physically connected and communicate with
each other.

Architectural Models:
These models describe the system in terms of the computational (processing)
and communication tasks performed by its parts.
It looks at both individual elements (like a single computer) and aggregate
elements (how these computers work together).
It also explains how the system components communicate and work together.

Fundamental Models:
This model takes an abstract approach to analyze a distributed system.
It focuses on key aspects of the system, such as:
Interaction models: How the different parts of the system communicate.
Failure models: How the system deals with failures, like when a part
stops working.
Security models: How the system ensures safety and prevents
unauthorized access.

Slide 2: Distributed System Design (Physical Models)

This slide dives deeper into Physical Models and how they evolved:

Baseline Physical Model:


A simple physical model where computers are connected by a network to send
and receive messages.
This model first appeared in the late 1970s and early 1980s when
technologies like LAN (Local Area Networks) and Ethernet were introduced.
It typically included 10 to 100 connected computers (nodes).
It had limited connectivity to the Internet and offered only basic services
like:
Sharing a local printer.
File servers (where data could be stored and accessed by multiple
users).
Email.
File transfer across the internet.

Slide 3: Distributed System Design (Physical Models)

This slide discusses how distributed systems evolved over time into Internet-scale
distributed systems.

Internet-Scale Distributed Systems:


These systems started to emerge in the 1990s, using the foundation of
earlier physical models, after the Internet experienced rapid growth (e.g., Google
started in 1996).
These systems exploit the Internet to become global, meaning they connect
users across the world.
High heterogeneity: These systems use various types of networks, computer
architectures (hardware setups), operating systems (Windows, Linux, etc.),
programming languages, and even different development teams.
They rely on open standards and middleware technologies like CORBA (a
technology that allows different programs to communicate) and web services to
connect different components.
Additional features include end-to-end Quality of Service (QoS), ensuring
that communication remains smooth and efficient across the internet.

Slide 4: Distributed System Design (Physical Models)

The focus now shifts to Contemporary Distributed Systems, which have emerged as
technology advanced.

Contemporary Distributed Systems:


As mobile phones became more popular, systems had to support service
discovery (finding services automatically) and spontaneous interoperation (working
together quickly and efficiently without needing much setup).
The rise of ubiquitous computing (where computers are embedded in everyday
objects like smart devices) led to changes in architecture. Instead of having
separate devices (like standalone computers), systems now involve computers
embedded in things we use daily.
With cloud computing and cluster computing, the focus shifted from using
single computers for specific tasks to pooling multiple computers to provide
services collectively.
These systems became more heterogeneous, meaning they included everything
from tiny devices (like sensors) to large computing networks (like grid computing).

Slide 5: Distributed System Design (Physical Models)

This slide introduces Distributed Systems of Systems, which are much larger and
more complex.

Distributed System of Systems:


These are ultra-large-scale (ULS) distributed systems that consist of
multiple subsystems. Each subsystem is a complete system on its own but works
together with other systems to perform a larger task.
Think of it like a big puzzle where each piece is a system that contributes
to the whole picture.
Example: An environmental management system for predicting floods.
It might use a sensor network to monitor rivers, floodplains, and other
environmental factors like tides.
These sensors work together to collect data that helps predict floods.

Slide 6: Architectural Models

This slide shifts the focus to Architectural Models of distributed systems. Here's
what it covers:

The Architecture of a System:


This refers to the structure of a system, meaning how its components
(parts) are arranged and how they relate to each other.
The goal is to design a system that can meet current and future demands.
For example, the system needs to be flexible enough to handle new
technology or new requirements in the future.
Key aspects of the design:
The system should be reliable (it works consistently).
It should be manageable (easy to control and fix).
It should be adaptable (able to adjust to new needs).
It should be cost-effective (not too expensive to build or maintain).
Just like a building's architecture shows how it looks and is structured,
the architecture of a system shows how the different parts fit together and
function.

You might also like