12.07.2015 Views

Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3. <strong>Architectural</strong> <strong>Pattern</strong>s 53<strong>Service</strong> 2<strong>Service</strong> 1 <strong>Service</strong> 3Message BusFigure 3.17: Example usage <strong>of</strong> Messaging patternperform operations on the systemServer– provides logic <strong>of</strong> the system.Relationships – - a user invoking operation on the clients invokes serversindirectly. The invocation is transparent. Clients can invoke servers butservers cannot invoke clients (see figure 3.18).Client 1Client 2ServerFigure 3.18: Example usage <strong>of</strong> Client Server pattern14. Explicit invocationOverview– the pattern determinates way <strong>of</strong> communication between elements<strong>of</strong> the system in distributed environment. This pattern is in fact avariation <strong>of</strong> Client-Server with one assumption. The assumption says thatconnections between Client and Server are known during design time.ElementsClient– is a frontend <strong>of</strong> an application.Client Logic– represents logic <strong>of</strong> the client.Client Broker– wraps connection <strong>to</strong> a supplierSupplier– application containing logicSupplier Logic– logic <strong>of</strong> the applicationSupplier Broker– wraps connection <strong>to</strong> a client

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!