Pattern - Division Of Labour - V 1.0 Dated May 16 2009

http://architecture-soa-bpm-eai.blogspot.com/ Tushar Jain Pattern Name: Pattern Class: Pattern ID:

Page 1 of 4 [email protected], [email protected]

Division of Labour Architectural: SOA A-SOA-0001

Version: Release Date:

1.0 May 16, 2009

Table of Content 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14.

Pattern Name...........................................................................................2 Also Known As..........................................................................................2 Class Name..............................................................................................2 Intent .....................................................................................................2 Motivation (Forces) ...................................................................................2 Applicability .............................................................................................2 Structure & Implemetation.........................................................................3 Participants..............................................................................................3 Collaboration............................................................................................4 Consequences ..........................................................................................4 Sample Code............................................................................................4 Known Uses .............................................................................................4 Related Patterns .......................................................................................4 Reference ................................................................................................4

http://architecture-soa-bpm-eai.blogspot.com/

Page 1 of 4

http://architecture-soa-bpm-eai.blogspot.com/ Tushar Jain

Page 2 of 4 [email protected], [email protected]

1. Pattern Name Division of Labour

2. Also Known As Specialization Separation of concern

3. Class Name Architectural: SOA

4. Intent As SOA gaining traction in main stream IT, it is becoming complex day by day. This increasing complexity at business and architectural has to be managed to keep SOA simple and neat. So taking cue from Object Oriented paradigm, this pattern proposes that a service must do only which it intend to do. Simply speaking services must be designed in such a way that they do what they are supposed to do.

5. Motivation (Forces) To better understand this pattern let consider a scenario. In banking environment there is mandate to create an account. This account may be of cheque account, saving account or current account. Due to legacy the said bank may have different systems to maintain these types of accounts. To handle this type of scenario it is recommended that there should be separate services which can create individual types of accounts.

6. Applicability 1. 2.

Underlying infrastructure on which a service will be written is made up of heterogeneous systems. A service is trying to do a big task which should be broken into smaller tasks keeping granularity and reuse in consideration.

http://architecture-soa-bpm-eai.blogspot.com/

Page 2 of 4

http://architecture-soa-bpm-eai.blogspot.com/ Tushar Jain

Page 3 of 4 [email protected], [email protected]

7. Structure & Implemetation

8. Participants Underlying monolithic applications/systems and services.

http://architecture-soa-bpm-eai.blogspot.com/

Page 3 of 4

http://architecture-soa-bpm-eai.blogspot.com/ Tushar Jain

Page 4 of 4 [email protected], [email protected]

9. Collaboration N/A

10. Consequences A. Positive a. Reuse of services b. Separation of logic c. Modular logic B. Negative a. Increased number of services

11. Sample Code N/A

12. Known Uses Need real life examples.

13. Related Patterns 1. In house encryption/decryption service in SaaS environment (Name to be decided)

14. Reference N/A

http://architecture-soa-bpm-eai.blogspot.com/

Page 4 of 4