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

Chapter 3. Architectural Patterns 69Pattern nameOccurrencesLayers – Model View Controller 3Broker – Client-Server 2Shared Repository – Presentation Abstraction2ControlLayers – Microkernel 2Shared Repository – Model View Controller2Client Server – Peer to Peer 2Shared Repository – Peer to Peer 2Shared Repository – C2 2Peer to Peer – C2 2Layers – Interpreter 2Layers – Client Server 2Pipes and Filters – Client Server 2Pipes and Filters – Shared Repository 2Client Server – Blackboard 2Broker – Shared Repository 2Broker – Half Sync/Half Async 2Shared Repository – Half Sync/Half 2AsyncClient Server – Half Sync/Half Async 2Table 3.6: Popularity of pairs of architectural patterns. Adopted from [38]However, there are many pairs of patterns, not all are included. Reviewers excludedsixty seven pairs that appeared only once.3.3.4 Representatives of categories in real systemsFilter 6: Removal of rarely interacting patternsTable presenting categories 3.3 with their representatives provides ten representativepatterns as follows: Layers, Pipes and Filters, Shared Repository,Microkernel, Reflection, Model View Controller, Half Sync/Half Async, ClientServer, Remote Procedure Call and Message Queueing. Additionally. Table 3.6,which is presenting popularity of particular patterns presents thirteen differentpatterns combined into pairs. The patters are as follows: Layers, Broker, SharedRepository, Pipes and Filters, Blackboard, Client Server, Presentation AbstractionController, Model View Controller, Microkernel, Peer to Peer, C2, Interpreter,Half Sync/Half Async. In order to minimize the list of potential patterns