Design Approach to SOA

[Former Member]

Hi,

I understand that to build services, it can be done inside-out or outside-in. As I come from a PI background, the outside-in approach makes sense to me.

However, is there any SAP guidelines on which approach to be used and more importantly why?

[Former Member · Accepted solution]

For any SOA project you have to perform service analysis and service design. These are the two main principles of SOA.

Service Design makes more sense for people who are developing services. In this phase you have to consider all permutation and combination of that service. I recommend you to follow this site (http://www.soaprinciples.com/) to understand best of SOA. I also suggest you to buy a book written by Thomus Erl ( SOA Principles of Service Design) - http://www.soabooks.com/psd/.

Part II: Design Principles

Chapter 6: Service Contracts (Standardization and Design)

Chapter 7: Service Coupling (Intra-Service and Consumer Dependencies)

Chapter 8: Service Abstraction (Information Hiding and Meta Abstraction Types)

Chapter 9: Service Reusability (Commercial and Agnostic Design)

Chapter 10: Service Autonomy (Processing Boundaries and Control)

Chapter 11: Service Statelessness (State Deferral and Stateless Design)

Chapter 12: Service Discoverability (Interpretability and Communication)

Chapter 13: Service Composability (Composition Member Design and Complex Compositions)

I believe you can find soft copy of these books from google also. Once you have deep knowledge of SOA you can correlate with eSOA .

Regards,

Farooq

Edited by: Farooq Farooqui on Oct 26, 2010 11:23 PM

[Former Member]

Hi,

Outside-in/Top-down approach is recommended approach but inside-out/bottom-up can be considered for quick wins and where reusability requirement of service is very low.

You can refer to [SAP SOA Handbook |http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40db4735-02f9-2a10-b198-a888a056bb67]for further information.

Regards,

Gourav