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

Chapter 3. Architectural Patterns 52data and provide them to clientsClient – uses repository to store data in it. Client also obtains data fromthe repository.Relationships – all the client elements are aware of the repository and canperform operations on it. The repository knows nothing about the clientsand cannot invoke them (see figure 3.16).Client 1 Client 2RepositoryClient 3Client 4 Client 5Figure 3.16: Example usage of Shared Repository pattern12. MessagingOverview – supports low coupling between elements of the system. Thispattern is also characterised by high maintainability and lower performance.ElementsMessage Bus – gets requests from services and invoke requested services.Service – presents business logic of the system.Relationships – Services are not aware of the location of other services.OnlyMessage Bus is known to services. Message Bus is aware of all the registeredservices (see figure 3.17).13. Client ServerOverview – - the pattern is dedicated for distributed architectures. Thepattern clearly separates frontend of the application from its logic.ElementsClient– it is a frontend of the application. This element allows a user to