95-702 Distributed Systems Lecture 1: Introduction 95-702Distributed - - PowerPoint PPT Presentation

95 702 distributed systems
SMART_READER_LITE
LIVE PREVIEW

95-702 Distributed Systems Lecture 1: Introduction 95-702Distributed - - PowerPoint PPT Presentation

95-702 Distributed Systems Lecture 1: Introduction 95-702Distributed Systems 1 Master of Information System Management Course Web Site http://www.andrew.cmu.edu/~mm6 95-702Distributed Systems 2 Master of Information System Management How


slide-1
SLIDE 1

95-702Distributed Systems

1

Master of Information System Management

95-702 Distributed Systems

Lecture 1: Introduction

slide-2
SLIDE 2

95-702Distributed Systems

2

Master of Information System Management

Course Web Site

  • http://www.andrew.cmu.edu/~mm6
slide-3
SLIDE 3

95-702Distributed Systems

3

Master of Information System Management

How Related to Other Courses

95-702 OCT 95-843 Service Oriented Architecture 95-774 Business Process Modeling 95-831 EA

slide-4
SLIDE 4

95-702Distributed Systems

4

Master of Information System Management

Course Technologies

  • IDE (Netbeans)
  • Java Web Applications (Glassfish)
  • Message Oriented Middleware

(Sun’s Message Queue )

  • Web Services (JDK 6, Glassfish)
  • Distributed Objects (Java RMI, and

EJB’s)

  • Mobile platform (Android)
slide-5
SLIDE 5

95-702Distributed Systems

5

Master of Information System Management

Getting Started Notes

  • See the schedule for instructions on

getting started with the course technologies.

  • The installation includes Netbeans,

Glassfish and the Android emulator.

  • Not to be turned in but please begin

this assignment now and let us know of any problems.

  • Homework 1 is also assigned.
slide-6
SLIDE 6

95-702Distributed Systems

6

Master of Information System Management

Structure of the Course

  • Lectures / class participation
  • Demonstrations (with your active

involvement)

  • Homework (pencil and paper and

programming) The secret is to start early.

  • Midterm
  • Final examination
slide-7
SLIDE 7

95-702Distributed Systems

7

Master of Information System Management

Readings

  • Readings from the required text

are assigned for each lecture -- read them in advance.

  • Readings from the web will also be

assigned.

  • For this week, read Coulouris

chapters 1 and 2

slide-8
SLIDE 8

95-702Distributed Systems

8

Master of Information System Management

Grading

  • Homework/Programming (5-7) 50%
  • Midterm 20%
  • Final Exam

30%

  • We will be very fussy about deadlines. One second

late is late.

  • All times are Adelaide times. Blackboard may show

Pittsburgh times. We will work from Adelaide time.

  • Use the discussion board for all queries with a

response that should be heard by the entire class.

slide-9
SLIDE 9

95-702Distributed Systems

9

Master of Information System Management

Characterization of Distributed Systems

  • Components are located on

networked computers and execute concurrently.

  • Components communicate and

coordinate only by passing messages.

  • There is no global clock.
  • What was the “Pony Express” like?
slide-10
SLIDE 10

95-702Distributed Systems

10

Master of Information System Management

Main Motivations for Constructing DS

  • Communications and Resource sharing.
  • We want to share:

Programs Data CPU cycles Files Printers Etc..

  • What do we share when we use “Cloud

Computing”?

slide-11
SLIDE 11

95-702Distributed Systems

11

Master of Information System Management

Challenges in Constructing DS

  • Heterogeneity of components
  • Openness
  • Security (Eve and Mallory)
  • Scalability
  • Failure handling
  • Concurrency of components
  • Transparency

Which of these are not challenges when constructing standalone systems?

slide-12
SLIDE 12

95-702Distributed Systems

12

Master of Information System Management

Example Distributed Systems

  • The internet

A collection of diverse networks A very large distributed system providing services such as email, file transfer, telnet, and recently, WWW, Web Services, and multimedia

  • Intranets (a portion of the internet

separately administrated) and connected to the internet via a router

  • Mobile and ubiquitous computing
  • Sensor networks
slide-13
SLIDE 13

95-702Distributed Systems

13

Master of Information System Management

intranet ISP desktop computer: backbone satellite link server: ☎ network link: ☎ ☎ ☎

A typical portion of the Internet

slide-14
SLIDE 14

95-702Distributed Systems

14

Master of Information System Management

A typical intranet

the rest of email server Web server

Desktop computers

File server router/firewall print and other servers

  • ther servers

print Local area network email server the Internet

slide-15
SLIDE 15

95-702Distributed Systems

15

Master of Information System Management

Portable and handheld devices in a distributed system

Laptop Mobile Printer Camera Internet Host intranet Home intranet WAP Wireless LAN phone gateway Host site

slide-16
SLIDE 16

95-702Distributed Systems

16

Master of Information System Management

Resource Sharing and the Web

  • A server is a running program on a

networked computer that accepts requests from programs running

  • n other computers to perform a

service and respond appropriately

  • The requesting processes are

referred to as clients

  • WWW, Web Services, networked

printers and email fit this model

slide-17
SLIDE 17

95-702Distributed Systems

17

Master of Information System Management

The World Wide Web(1)

  • Created by Sir Tim Berners-Lee at

European centre for nuclear research (CERN) in Switzerland in 1989 (Knighted 2003)

  • Provides a hypertext structure allowing

documents to contain links to other documents

  • Is an open system (can be extended

and implemented in new ways, standards are public and widely implemented)

slide-18
SLIDE 18

95-702Distributed Systems

18

Master of Information System Management

The World Wide Web (2)

  • The web is based on three main

standard technological components (1) HTML for presentation of content and Links (2) URL’s to point to a resource and specify a protocol (3) HTTP to describe the request and reply protocol

slide-19
SLIDE 19

95-702Distributed Systems

19

Master of Information System Management

Web servers and web browsers

Internet Browsers Web servers www.google.com www.cdk3.net www.w3c.org Protocols Activity.html http://www.w3c.org/Protocols/Activity.html http://www.google.comlsearch?q=kindberg http://www.cdk3.net/ File system of www.w3c.org

slide-20
SLIDE 20

95-702Distributed Systems

20

Master of Information System Management

A Request May Cause

  • A simple file transfer
  • A process to be run on the server

and content sent to the browser (CGI programs, servlets, JSP pages, etc.)

  • Program code to be downloaded

and executed in the browser (JavaScript, Applets, Java Web Start, etc.)

slide-21
SLIDE 21

95-702Distributed Systems

21

Master of Information System Management

Challenges to DS Design(1)

  • Heterogeneity applies to

Networks (Ethernet, Wireless,..) Computer Hardware (PC’s, PDA’s,..) Operating Systems (Linux, OS X, Windows,..) Programming Languages ( Java, C++, C#,..) Different developers

  • Middleware provides a programming

abstraction that addresses these issues

slide-22
SLIDE 22

95-702Distributed Systems

22

Master of Information System Management

Challenges to DS Design(2)

  • Open
  • - The system can be extended and

re-implemented in a variety of ways

  • - The key specifications are

published

  • - The system is independent of a

particular vendor

slide-23
SLIDE 23

95-702Distributed Systems

23

Master of Information System Management

Challenges to DS Design(3)

  • Security

Some resources are highly valued. Confidentiality is often required. Integrity is often required. Availability is often essential.

  • Cryptography will help with much of

this.

  • Denial of Service and Mobile Code are

not yet easy to handle

slide-24
SLIDE 24

95-702Distributed Systems

24

Master of Information System Management

Challenges to DS Design(4)

  • Scalability

A system is described as scalable if it will remain effective when there is a significant increase in the number of resources and the number of users For a system with n users to be scalable the quantity of physical resources required to support them should be O(n).

slide-25
SLIDE 25

95-702Distributed Systems

25

Master of Information System Management

Challenges to DS Design(5)

  • Scalability

For system to be scalable, the loss in performance attributed to additional users or resources should be O(Log n) Examples of bottleneck avoidance

  • distributed algorithms
  • Domain Name System
  • caching
  • replication
slide-26
SLIDE 26

95-702Distributed Systems

26

Master of Information System Management

Computers in the Internet

Date Computers Web servers 1979, Dec. 188 1989, July 130,000 1999, July 56,218,000 5,560,866

The internet has been scalable and extensible. However, the 32 bit IP address was too small. Moving to IPv6, 128 bits.

slide-27
SLIDE 27

95-702Distributed Systems

27

Master of Information System Management

Computers vs. Web Servers on the Internet

Date Computers Web servers Percentage 1993, July 1,776,000 130 0.008 1995, July 6,642,000 23,500 0.4 1997, July 19,540,000 1,203,096 6 1999, July 56,218,000 6,598,697 12

Netcraft reports 118,000,000 web sites active in May of 2007.

slide-28
SLIDE 28

95-702Distributed Systems

28

Master of Information System Management

Challenges to DS Design(6)

  • Failure Handling

Particularly difficult in DS Failures are often partial Issues include: Detecting failures Masking or hiding failures with,e.g.,retries Tolerating Failures Recovery from failures or rolling back changes

slide-29
SLIDE 29

95-702Distributed Systems

29

Master of Information System Management

Challenges to DS Design(7)

  • Concurrency

Multiple client requests are often allowed to take place concurrently. Forcing one request at a time would limit throughput. Standard techniques exist to protect against conflicts, E.g., Java and C# synchronization.

slide-30
SLIDE 30

95-702Distributed Systems

30

Master of Information System Management

Challenges to DS Design(8)

Access transparency: enables local and remote resources to be accessed using

identical operations. Location transparency: enables resources to be accessed without knowledge of their location.

Concurrency transparency: enables several processes to operate concurrently

using shared resources without interference between them. Replication transparency: enables multiple instances of resources to be used to increase reliability and performance without knowledge of the replicas by users or application programmers.

  • Types of Transparency (or concealment)
slide-31
SLIDE 31

95-702Distributed Systems

31

Master of Information System Management

Challenges to DS Design(9)

Failure transparency: enables the concealment of faults,allowing users and application programs to complete their tasks despite the failure of hardware or software components. Mobility transparency: allows the movement of resources and clients within a system without affecting the operation of users or programs. Performance transparency: allows the system to be reconfigured to improve performance as loads vary. Scaling transparency: allows the system and applications to expand in scale without change to the system structure or the application algorithms.

slide-32
SLIDE 32

95-702Distributed Systems

32

Master of Information System Management

Pitfalls when Developing Distributed Systems

Some false assumptions that may be made by designers:

  • The network is reliable.
  • The network is secure.
  • The network environment is homogeneous.
  • Latency is zero.
  • Bandwidth is infinite.
  • Transport cost is zero.
  • There is one administrator.