Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The history of distributed computing and the important question of how communication should be presented to the programmer. It discusses different communication abstractions such as inter-process communication (ipc), remote procedure calls (rpc), distributed shared memory, and object-oriented model. The document also covers inter-process communication using unix sockets, rpc implementation, distributed objects using corba, and distributed shared memory. Additionally, it touches upon group communication and the client-server model.
Typology: Study notes
1 / 12
This page cannot be seen from the preview
Don't miss anything!
I see one machine running one program
What should I run where?
Communication is transparent
Communication is explicit
main() { … function() … }
Machine A
function() { send message wait for reply return }
Machine B
parent() { wait for call call function() send reply }
function() { … }
main () { … obj.method() … }
Object Request Broker
Distributed Objects
Find object
Code segment
Data segment
Machine A Machine B
Machine C
Machine D
Machine E
Program
No central point of failure Potentially more scalable
More difficult to program
Client
Server
Port
bind() Well-known port listen()
accept()
read()
write()
close()
eof()?
write()
read()
connect()
socket()
socket()
close()
Client
Server
Web Server
80 Listen queue
Web Server
80 Listen queue
Client
connect()
Request from (IP, port)
