精通WCF 4：微软SOA实战指南

5星 · 超过95%的资源需积分: 0 114 浏览量更新于2024-07-27 收藏 10.16MB PDF 举报

"Pro WCF 4 Practical Microsoft SOA Implementation" 本书是关于Windows Communication Foundation (WCF) 的专业指南，特别关注于WCF在实现面向服务架构（SOA）中的实践应用。作者Nishith Pathak深入浅出地介绍了如何创建安全、可靠且互操作的服务，适合对.NET框架有一定了解并希望提升WCF技术能力的开发人员。第一部分：引入Windows Communication Foundation 这部分主要介绍了WCF的基本概念以及它与SOA的关系。在第1章中，读者会了解到WCF作为.NET Framework的一部分，是如何提供服务导向的通信基础的，同时也会接触到SOA的基本原理。第2章探讨了WCF 4版本的新特性和改进，帮助读者了解自WCF早期版本以来的发展。第3章则深入到WCF的编程模型，包括服务合同、绑定、行为和服务主机等关键概念。第二部分：使用WCF编程这部分从实际操作的角度出发，教读者如何安装和创建WCF服务。第4章详述了服务的安装过程，并展示了创建服务的基础步骤。第5章讨论了服务的托管和消费，涵盖了自我托管、IIS托管以及其他托管选项。第6章则涉及服务的管理和生命周期管理，包括配置、调试和监控等方面。第三部分：WCF高级主题这部分深入讨论了WCF的高级特性。第7章讲解了WCF的安全实现，包括身份验证、授权和加密等。第8章涵盖了可靠消息传递和队列通信，这是实现高可用性和容错性的关键。第9章介绍了如何在WCF中使用事务，确保数据一致性。第10章讨论了与COM+的集成，这对于企业级应用的迁移和整合至关重要。第11章则专注于数据处理，包括数据契约、XML序列化和数据转换等。通过这本书，开发者不仅可以掌握WCF的基本用法，还能了解到如何利用其高级功能来构建复杂的企业级应用。书中的案例和实战指导将帮助读者在实际项目中有效地应用这些知识。此外，附录和其他辅助材料提供了方便的索引和快速参考，使学习和查找信息变得更加便捷。

CHAPTER 1 ■ WCF AND SOA BASICS

■Note Simply put, SOAP is a lightweight communication protocol for web services based on XML. It is used to

exchange structured and typed information between systems. SOAP allows you to invoke methods on remote

machines without knowing specific details of the platform or software running on those machines. XML is used to

represent the data, while the data is structured according to the SOAP schema. The only thing both the consumer

and provider need to agree on is this common schema, defined by SOAP. Overall, SOAP keeps things as simple as

possible and provides minimum functionality. SOAP used to stand for “Simple Object Access Protocol,” but the

W3C dropped that name when the focus shifted from object access to object interoperability via a generalized XML

messaging format as part of SOAP 1.2.

XML web services are designed with interoperability in mind, and are easily callable from non-

Windows platforms. It is common to confuse web services with .NET Remoting. Web services and .NET

Remoting are related, but web services have a more simplified programming model than .NET

Remoting. In other words, .NET Remoting and web services look similar from a high-level architecture

level, but they differ in the way they work. For example, they both have different ways of serializing data

into messages. .NET Remoting supports RPC-based communication by default, and web services

support message-based communication by default. Web services rely on XML Schema for data types,

and .NET Remoting relies on the CLR. You can use .NET Remoting to build web services, but the WSDL

generated by .NET Remoting is not widely adopted and might be ignored by some clients. Though you

can use either for creating components, .NET Remoting is suitable for creating components to be used

by your own application running in the .NET environment, and XML web services create components

that can be accessible to any application connected via the Internet.

Through web services, Microsoft wants to achieve the best of both worlds—web development and

component-based development. Web services were the first step toward service orientation, which is a

set of guiding principles for developing loosely coupled distributed applications. SOA is a vision of

services that have well-defined interfaces. These loosely coupled interfaces communicate through

messages described by the XML Schema Definition (XSD) and through the message patterns described

by WSDL. This provides for a great base architecture for building distributed applications. Since a web

service and its clients are independent of each other, they need to adhere only to the XSD and WSDL

document standards in order to communicate.

The next Microsoft offering to address SOA is WCF. We’ll now discuss how WCF complements web

services and enhances their value.

What Does WCF Solve?

WCF is not just another way of creating a distributed solution—it also provides a number of benefits

compared to its predecessors. If you look at the background of WCF, you’ll find that work on WCF

started with the release of .NET. Microsoft unveiled this technology at the 2003 Microsoft Product

Developers Conference in Los Angeles, California. In other words, it has taken years to build and come

to market. WCF addresses lots of issues; Figure 1–2 shows the three main design goals of WCF.

CHAPTER 1 ■ WCF AND SOA BASICS

one clean and simple API. In other words, WCF brings the entire existing distributed stack under one

roof. All you need to do as a developer is reference the System.ServiceModel assembly and import its

namespace.

As shown in Figure 1–3, WCF subsumes the best of all the distributed technologies. WCF brings

together the efficiency of ASMX, the ability to adopt transactions with Enterprise Services using only

attributes, the extensibility and flexibility of .NET Remoting, the supremacy of MSMQ for building

queued applications, and WSE’s interoperability through WS-*. Microsoft took all these capabilities and

built a single, steady infrastructure in the form of WCF.

Figure 1–3. Unification of distributed technologies

Interoperability Across Platforms

Most of the big software companies are developing software using proprietary protocols that are tightly

coupled with a specific platform. This software succumbs to the problem of not being interoperable with

other software running on different platforms. When you look at any large enterprise in particular, you

often notice a number of disparate systems built and bought over periods of time. Often these systems

are incompatible with one another. The ability to link the systems becomes a crucial need for a large

number of organizations. In addition, newly developed applications need to interoperate with the

existing platforms, and the business needs to support applications written in different programming

languages with different technologies. Also, companies need seamless interoperability across the

organization between purchased software from different software vendors.

Interoperability was a major issue for all the major software vendors, and they all wanted to use a

widely accepted and adopted suite of protocols. To solve this issue, industry leaders such as Microsoft,

IBM, BEA, and Sun formed the Web Services Interoperability (WS-I) organization, which has developed a

suite of specifications that, if adopted, allows software to seamlessly communicate with other software

running on different platforms.

CHAPTER 1 ■ WCF AND SOA BASICS

Not only can WCF interact with its counterparts from other vendors, but it can also exist peacefully

with predecessors including COM+ and Enterprise Services. For developers, this drastically reduces the

amount of infrastructure code required to achieve heterogeneous interoperability.

WCF As a Service-Oriented Development Tool

WCF is the first programming model built from the ground up to provide explicit service-oriented

application development and future-ready business orientation. Service orientation is not a technology,

but a design concept. Service orientation uses the best practices for building today’s distributed

applications. Purists and gurus of distributed applications consider service orientation to be the design

guideline for overcoming some of the complication in designing loosely coupled applications. Service

orientation is not a new concept—it has been around for some years. Some projects have tried to

implement the concept of service orientation by tweaking existing distributed technologies; these

projects have always demanded a framework that has built-in support for service orientation. Although

existing distributed technologies can offer the groundwork for interoperability and integration, a new

platform was required—a new infrastructure that makes it much easier to build these distributed

technologies.

Although it may seem surprising, one of the most intriguing parts of designing a service is deciding

how it should expose its functionality to the outside world. The level of granularity of the service quite

often is one of the most heated topics of debate within an organization. If the service is “finely grained,”

then the focus is on exchanging small amounts of data to complete a specific task. This is usually

associated with the more traditional RPC communication style. Any additional tasks, if required, are

invoked similarly. Since message-based service invocations are expensive, finely grained approaches

aren’t practical in most situations because the overhead of transmitting and processing many individual

messages isn’t acceptable. On the other hand, coarse-grained services expose more functionality within

the same service invocation, combining many small tasks. This relates to fewer messages transmitted

with more data, as opposed to many messages with less data. In other words, coarse-grained services are

less chatty, which results in less overhead on both ends of the service, allowing it to scale better.

When designing services, you need to think beyond basic object-oriented design principles and use

the four tenets of service orientation discussed previously in this chapter as the guiding principles.

Figure 1–5 shows the four tenets of service orientation. One of the challenges in developing WCF is

shifting developers’ mindsets away from building distributed systems in terms of objects and

components, and toward building distributed systems as services. WCF offers that foundation for

service-oriented applications built on Windows; it will be basic to the SOA efforts of many organizations.

剩余457页未读，继续阅读

zhujiazhao123

粉丝: 5
资源: 7

精通WCF 4：微软SOA实战指南

WCF4高级编程Professional.WCF.4

WCF教程(Pro_WCF_Practical_Microsoft_SOA_Implementation-3297)

Apress.Pro.WCF.Practical.Microsoft.SOA.Implementation.Jan.rar

精通WCF 4：微软SOA实战指南（第2版）

WCF 4实战：微软SOA安全与高级实施指南

WCF 4实战：微软SOA专家构建安全可靠的微软服务

深入实践：WCF4与SOA服务实现

WCF高级编程

[WCF系列] WCF 经典原版著作 合集

精通WCF4：微软.NET框架下的数据通信接口

最新资源

[WCF系列] WCF 经典原版著作合集