Communication in Distributed Systems

Communication in Distributed Systems
Issues in communication (today) Message-oriented Communication Remote Procedure Calls

Transparency but poor for passing references
Remote Method Invocation

RMIs are essentially RPCs but specific to remote objects System wide references passed as parameters
Stream-oriented Communication
Computer Science
CS677: Distributed OS
Lecture 6, page 1
Communication Between Processes
Unstructured communication
Use shared memory or shared data structures
Structured communication
Use explicit messages (IPCs)
Distributed Systems: both need low-level communication support (why?)

Computer Science
CS677: Distributed OS Lecture 6, page 2
Communication Protocols
Protocols are agreements/rules on communication Protocols could be connection-oriented or connectionless
2-1
Computer Science
Lecture 6, page 3
Layered Protocols
A typical message as it appears on the network.
2-2
Computer Science
Lecture 6, page 4
Client-Server TCP
a) b)
2-4 Normal operation of TCP. Transactional TCP.
Computer Science
Lecture 6, page 5
Middleware Protocols
Middleware: layer that resides between an OS and an application
May implement general-purpose protocols that warrant their own layers Example: distributed commit
2-5
Computer Science
Lecture 6, page 6
Client-Server Communication Model

Structure: group of servers offering service to clients Based on a request/response paradigm Techniques:
Socket, remote procedure calls (RPC), Remote Method Invocation (RMI)
client kernel
file server
process server
terminal server
kernel
kernel
kernel
Computer Science
Lecture 6, page 7
Issues in Client-Server Communication

Addressing Blocking versus non-blocking Buffered versus unbuffered Reliable versus unreliable Server architecture: concurrent versus sequential Scalability
Computer Science
Lecture 6, page 8
Addressing Issues
Question: how is the server located? Hard-wired address
Machine address and process address are known a priori
user
server
Broadcast-based
Server chooses address from a sparse address space Client broadcasts request Can cache response for future
user
server
NS
user
server
Locate address via name server

Computer Science
Blocking versus Non-blocking

Blocking communication (synchronous)
Send blocks until message is actually sent Receive blocks until message is actually received
Non-blocking communication (asynchronous)

Send returns immediately Return does not block either
Examples:
Computer Science
Lecture 6, page 10
Buffering Issues
Unbuffered communication
Server must call receive before client can call send
user server
Buffered communication
Client send to a mailbox Server receives from a mailbox
user
server
Computer Science
Lecture 6, page 11
Reliability
Need acknowledgements (ACKs) Applications handle ACKs ACKs for both request and reply
reply ACK
User
Reply acts as ACK for request
reply
Reliable communication on unreliable channels

Transport protocol handles lost messages
Computer Science
Server
Lecture 6, page 12
Reliable channel
request
Server
Unreliable channel
User
request ACK
Server Architecture
Sequential
Serve one request at a time Can service multiple requests by employing events and asynchronous communication
Concurrent
Server spawns a process or thread to service each request Can also use a pre-spawned pool of threads/processes (apache)
Thus servers could be

Pure-sequential, event-based, thread-based, process-based
Discussion: which architecture is most efficient?

Computer Science
Scalability
Question:How can you scale the server capacity? Buy bigger machine! Replicate Distribute data and/or algorithms Ship code instead of data Cache
Computer Science
Lecture 6, page 14
To Push or Pull ?
Client-pull architecture
Clients pull data from servers (by sending requests) Example: HTTP Pro: stateless servers, failures are each to handle Con: limited scalability
Server-push architecture
Servers push data to client Example: video streaming, stock tickers Pro: more scalable, Con: stateful servers, less resilient to failure
When/how-often to push or pull?

Computer Science
Group Communication
One-to-many communication: useful for distributed applications Issues:
Group characteristics: Static/dynamic, open/closed Group addressing Multicast, broadcast, application-level multicast (unicast) Atomicity Message ordering Scalability
Computer Science
Putting it all together: Email

User uses mail client to compose a message Mail client connects to mail server Mail server looks up address to destination mail server Mail server sets up a connection and passes the mail to destination mail server Destination stores mail in input buffer (user mailbox) Recipient checks mail at a later time
Computer Science
Lecture 6, page 17
Email: Design Considerations

Structured or unstructured? Addressing? Blocking/non-blocking? Buffered or unbuffered? Reliable or unreliable? Server architecture Scalability Push or pull? Group communication
Computer Science

Communication in Distributed Systems

Uploaded by

Copyright:

Available Formats

Communication in Distributed Systems

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Communication in Distributed Systems

Uploaded by

Copyright:

Available Formats

Communication in Distributed Systems

Issues in communication (today) Message-oriented Communication Remote Procedure Calls

Remote Method Invocation

Communication Between Processes

Distributed Systems: both need low-level communication support (why?)

2-4 Normal operation of TCP. Transactional TCP.

Client-Server Communication Model

Issues in Client-Server Communication

Locate address via name server

Blocking versus Non-blocking

Non-blocking communication (asynchronous)

Reply acts as ACK for request

Reliable communication on unreliable channels

Thus servers could be

Discussion: which architecture is most efficient?

When/how-often to push or pull?

Putting it all together: Email

Email: Design Considerations

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.