WCF has a layered architecture that offers ample support for developing various distributed applications. The architecture is explained below in detail.
wcf有一个分层的架构，为开发不同的分布式应用提供了足够的支持。架构图的细节如下图所示
Contracts 契约
The contracts layer is just next to the application layer and contains information similar to that of a real-world contract that specifies the operation of a service and the kind of accessible information it will make. Contracts are basically of four types discussed below in brief:
契约层紧挨着应用层，它包含的信息和现实世界中的界面类似，指定了服务的操作，服务产生的可访问信息的类型。简单来说，契约有以下4种类型
Service contract - This contract provides information to the client as well as to the outer world about the offerings of the endpoint, and the protocols to be used in the communication process.
Data contract - The data exchanged by a service is defined by a data contract. Both the client and the service has to be in agreement with the data contract.
Message contract - A data contract is controlled by a message contract. It primarily does the customization of the type formatting of the SOAP message parameters. Here, it should be mentioned that WCF employs SOAP format for the purpose of communication. SOAP stands for Simple Object Access Protocol.
Policy and Binding - There are certain pre-conditions for communication with a service, and such conditions are defined by policy and binding contract. A client needs to follow this contract.
1.服务契约：提供给信息给客户端以及外部世界，信息是关于endpoint提供的，以及进程间通讯使用的协议
2.数据契约：由服务进行交换的数据，定义在数据契约中。 客户端和服务端都必须与数据契约保持一致
3.消息契约：数据契约由消息契约进行控制。它主要用来处理soap消息参数格式的自定义类型。这里，它应该提到wcf所使用的用于通信目的的soap格式。 soap表示Simple Object Access Protocol.
4.策略和绑定：有一些和服务进行通信的前提条件，比如由策略以及绑定契约所定义的条件。客户端需要按照这个契约来处理
Service Runtime 服务运行时
The service runtime layer is just below the contracts layer. It specifies the various service behaviors that occur during runtime. There are many types of behaviors that can undergo configuration and come under the service runtime.
service runtime层在契约层下面。它指明了在运行时发生的各种服务行为。有许多类型的行为可以进行配置，并且在服务运行时出现。
Throttling Behavior - Manages the number of messages processed.
Error Behavior - Defines the result of any internal service error occurrence.
Metadata Behavior - Specifies the availability of metadata to the outside world.
Instance Behavior - Defines the number of instances that needs to be created to make them available for the client.
Transaction Behavior - Enables a change in transaction state in case of any failure.
Dispatch Behavior - Controls the way by which a message gets processed by the infrastructure of WCF.
Concurrency Behavior - Controls the functions that run parallel during a client-server communication.
Parameter Filtering - Features the process of validation of parameters to a method before it gets invoked.
1.限制行为：控制能够处理的消息的数量
2.错误行为：定义了任何内部错误发生时的结果
3.元数据行为：详细说明了元数据对外部世界的可用性
4.实例行为：定义了需要创建的实例的数量，并使得他们对客户端可用
5.事务行为：万一遇到故障，确保事务会有一个变化
6.调度行为：控制wcf底层处理消息的方式
7.并发行为：控制客户端和服务端通信时的并发功能
8.参数过滤：实现了在调用方法之前，检查参数的有效性
Messaging 消息
This layer, composed of several channels, mainly deals with the message content to be communicated between two endpoints. A set of channels form a channel stack and the two major types of channels that comprise the channel stack are the following ones:
消息层，由若干个信道组成。消息主要用于处理2个终结点之间的通信内容。一系列的信道形成了信道栈，组成信道栈的2个主要信道类型如下：
Transport Channels - These channels are present at the bottom of a stack and are accountable for sending and receiving messages using transport protocols like HTTP, TCP, Peer-to-Peer, Named Pipes, and MSMQ.
Protocol Channels - Present at the top of a stack, these channels also known as layered channels, implement wire-level protocols by modifying messages.
1.传输信道：传输信道位于栈的底部，负责使用传输协议来发送和接收消息，使用的协议包括HTTP，TCP，P2P，命名管道以及消息队列
2.协议信道：协议信道在栈的顶部，协议信道也被称为分层信道，通过无线协议来修改消息
Activation and Hosting 激活与宿主
The last layer of WCF architecture is the place where services are actually hosted or can be executed for easy access by the client. This is done by various mechanisms discussed below in brief.
wcf架构的最后一层，是服务实际寄宿的地方或者是执行起来后客户端可以轻易访问。简单来说，这是由一下各种机制来完成的
IIS - IIS stands for Internet Information Service. It offers a myriad of advantages using the HTTP protocol by a service. Here, it is not required to have the host code for activating the service code; instead, the service code gets activated automatically.
Windows Activation Service - This is popularly known as WAS and comes with IIS 7.0. Both HTTP and non-HTTP based communication is possible here by using TCP or Namedpipe protocols.
Self-hosting - This is a mechanism by which a WCF service gets self-hosted as a console application. This mechanism offers amazing flexibility in terms of choosing the desired protocols and setting own addressing scheme.
Windows Service - Hosting a WCF service with this mechanism is advantageous, as the services then remain activated and accessible to the client due to no runtime activation.
1.IIS：互联网信息服务，通过一个使用HTTP协议的服务，它可以提供大量的优势。它不要求host代码来激活service代码，service code会自行激活。
2.WAS：windows激活服务，这个适合IIS7.0一起发布的。通过使用TCP或者命名管道协议，不管是基于http或者非http的通信都是可能的
3.自托管：wcf服务通过自托管成一个控制台应用来实现的机制，这个机制在选择所需的协议以及设置它自己的地址模式时有这惊人的灵活性
4.windows服务：使用这种机制托管wcf是有益的，因为不需要运行时激活，服务就可以一直保持激活状态并且对客户端可以访问
最后附上中文的架构图：图片是百度搜索的，不知道出处是哪里
