SOA中补偿缺乏继承的模式(Patterns for Compensating Lack of Inheritance in SOA)

 我发现基类的继承和概念是OOP的最强点。 但是在SOA中并不鼓励这样做。 那么，在SOA中克服这种限制的流行模式是什么？ 能否请您提供解释这些模式的教程（在WCF中使用代码演示）？ 
 
 注意：这不是关于SOA中可用模式的一般问题。 但它更具体到上述问题。 
 
 注意：我正在使用WCF进行SOA。 
 
 
 读： 
 
 
 
 “不要在Design中使用Abstract Base类; 但在建模/分析中“ 
 
 
 如何真正实现SOA架构？ 
 
 
 如何在面向服务的体系结构中处理Java多态性 
 
 
 如何加快SOA的速度？ 
 
 
 什么是面向服务的架构？ 
 
 
 DDD和SOA真的能很好地协同工作吗？ 
 
 
 SOA和WCF设计问题：这是一个不寻常的系统设计吗？ 
 
 
 设计WCF数据合同和操作 
 
 
 C＃4.0中的Expando对象 
 

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:
 
 
 
“Do not use Abstract Base class in Design; but in Modeling/Analysis”
 
 
How is an SOA architecture really supposed to be implemented?
 
 
How to deal with Java Polymorphism in Service Oriented Architecture
 
 
How to get up to speed on SOA?
 
 
What is service-oriented architecture?
 
 
Do DDD and SOA really play well together?
 
 
SOA and WCF design questions: Is this an unusual system design?
 
 
Designing WCF data contracts and operations
 
 
Expando Objects in C# 4.0
 

原文：https://stackoverflow.com/questions/9478015