Lernmaterialien für Distributed Systems an der Frankfurt University of Applied Sciences

Incremental in-/decrease of the computing power as well as the load balance is possible

- transmission of clean data in trough the network is easier

-sharing/distributing of code (functions/methods) is difficult

allows the system and applications

to expand in scale without change to the system structure or the

application algorithms

Regardless of how resource access and representation has to be performed on each individual computing entity, the users of a distributed system should always access resources in a single uniform way

Users of a distributed system should not have to be aware of where a resource is physically located.

Users should not be aware of whether a resource or computing entity possesses the ability to move to a different physical or logical location.

-Finding Services (who offers what kind of service?)

-Binding (How do i connect to a service)

-Data Transfer (Method Calling and transferring Object)

-Temporary Binding between Client and server
-Client blocks server and vice versa

e.g. Telephone call

-No temporary binding between client and server
-Client/server handle request when/if they would like/can to

e.g. Email, Bulletin Board

REST is resource oriented

-one resource for one use case

-one URL for one use case

-How resources get manipulated

-Part of the resource state

--Transferred between client and server

- GET      retrieve copy of a resource

- POST   create resource