Patterns for Compensating Lack of Inheritance in SOA

Question

I find Inheritance and concept of base class as the strongest point of OOP. But this is not encouraged in SOA. So, what are the popular patterns for overcoming this limitation in SOA? Could you please provide tutorials that explains (with code demonstration in WCF) these patterns?

Note: This is NOT a general question about patterns available in SOA. But it is more specific to the above mentioned problem.

Note: I am using WCF for SOA.

---

Reading:

1. “Do not use Abstract Base class in Design; but in Modeling/Analysis”

2. How is an SOA architecture really supposed to be implemented?

3. How to deal with Java Polymorphism in Service Oriented Architecture

4. How to get up to speed on SOA?

5. What is service-oriented architecture?

6. Do DDD and SOA really play well together?

7. SOA and WCF design questions: Is this an unusual system design?

8. Designing WCF data contracts and operations

9. Expando Objects in C# 4.0

Answer 1

No matter whether or not you think about SOA as implemented by SOAP, REST or messaging, services are document-centric. Services are not object-oriented.

While polymorphism is a strong design tool in OOD, it's not applicable in SOA because SOA modeling doesn't involve classes.