com/ Page 1 of 4
Tushar Jain tusjain@yahoo.com, tusjain@gmail.com
Table of Content
1. Pattern Name...........................................................................................2
2. Also Known As..........................................................................................2
3. Class Name..............................................................................................2
4. Intent .....................................................................................................2
5. Motivation (Forces) ...................................................................................2
6. Applicability .............................................................................................2
7. Structure .................................................................................................2
8. Participants..............................................................................................3
9. Collaboration............................................................................................3
10. Consequences ..........................................................................................3
11. Implementation........................................................................................3
12. Sample Code............................................................................................3
13. Known Uses .............................................................................................3
14. Related Patterns .......................................................................................4
15. Reference ................................................................................................4
http://architecture-soa-bpm-eai.blogspot.com/ Page 1 of 4
http://architecture-soa-bpm-eai.blogspot.com/ Page 2 of 4
Tushar Jain tusjain@yahoo.com, tusjain@gmail.com
1. Pattern Name
Service Discovery - Direct
2. Also Known As
N/A
3. Class Name
SOA Architectural
4. Intent
The one of the primary tenant of SOA is service discovery. Service
Discovery can be done at Design Time or at Run Time.
5. Motivation (Forces)
Simplicity, Point to Point integration and run time performance are
motivation behind this pattern.
6. Applicability
This pattern is used during conceptualization of SOA within
enterprise and when IT ecosystem is simple enough which do not
warrant any Run time discovery of services.
7. Structure
http://architecture-soa-bpm-eai.blogspot.com/ Page 2 of 4
http://architecture-soa-bpm-eai.blogspot.com/ Page 3 of 4
Tushar Jain tusjain@yahoo.com, tusjain@gmail.com
8. Participants
Service Consumer
Service Provider
9. Collaboration
N/A
10. Consequences
Due to design time binding of consumer and provider following are
the consequences:
11. Implementation
N/A
http://architecture-soa-bpm-eai.blogspot.com/ Page 3 of 4
http://architecture-soa-bpm-eai.blogspot.com/ Page 4 of 4
Tushar Jain tusjain@yahoo.com, tusjain@gmail.com
Design Time
Run Time
Design Time
Run Time
Design Time
Run Time
Run Time
15. Reference
N/A
http://architecture-soa-bpm-eai.blogspot.com/ Page 4 of 4