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

需积分: 0 12 浏览量更新于2024-07-29 收藏 10.16MB PDF 举报

"C#技术书籍 Pro WCF4 SOA" 本书是关于C#编程中的Windows Communication Foundation (WCF) 和面向服务架构 (SOA) 实施的专业指南，旨在帮助开发者掌握下一代安全、可靠和互操作性服务的创建。书中详细介绍了WCF 4版本的新特性，以及如何在实际项目中运用WCF。书的内容结构分为三个部分： 1. **Part I: Introducing Windows Communication Foundation** 这部分介绍了WCF和SOA的基础知识，包括WCF的基本概念、WCF 4的新功能，以及WCF编程模型的探索。读者将了解WCF如何作为.NET Framework的一部分，为构建分布式应用程序提供服务，并学习到WCF如何支持SOA设计原则。 - 第1章：WCF和SOA基础知识，讲解了WCF的背景、目标以及SOA的基本理念。 - 第2章：WCF 4的新特性，探讨了与旧版本相比WCF 4带来的改进和增强。 - 第3章：探索WCF编程模型，深入研究WCF的服务契约、数据契约和服务行为等核心概念。 2. **Part II: Programming with WCF** 这部分侧重于如何实际安装、创建、托管和消费WCF服务，提供了详细的实践指导。 - 第4章：安装和创建WCF服务，涵盖了服务配置、服务主机的选择以及服务的部署。 - 第5章：托管和消费WCF服务，讨论了服务的生命周期管理，包括服务的启动、停止以及客户端如何与服务交互。 - 第6章：管理WCF服务，涵盖了服务的监控、调试和故障排除策略。 3. **Part III: Advanced Topics in WCF** 这部分深入探讨了WCF的高级主题，如安全性、可靠消息传递、队列通信、事务处理以及与COM+的集成，以及如何处理和操作数据。 - 第7章：实现WCF安全，详细介绍了身份验证、授权、加密等安全机制的实现。 - 第8章：实现可靠消息传递和队列通信，讲解了如何确保消息的传输可靠性，以及如何利用队列提高系统的健壮性。 - 第9章：使用WCF中的事务，介绍如何在分布式环境中协调事务，确保数据的一致性。 - 第10章：与COM+的集成，展示了如何将WCF服务与现有的COM+应用程序进行无缝集成。 - 第11章：处理数据，探讨了数据契约、数据绑定和数据序列化等相关技术。书的作者Nishith Pathak通过这本书分享了他的专业知识和经验，使得读者能够逐步从基础到高级，全面掌握使用C#和WCF 4构建SOA应用的技能。此外，书中的附录还提供了方便读者查找的书签和目录链接，以及作者和技术审阅者的简介和致谢。《Pro WCF4: Practical Microsoft SOA Implementation》是一本全面的指南，对于想要深入理解并有效利用WCF构建现代企业级SOA应用的C#开发者来说，是不可或缺的参考资料。

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页未读，继续阅读

liukun_allen

粉丝: 0
资源: 1

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

Pro WCF 4 Practical Microsoft SOA Implementation

使用WCF实现SOA面向服务编程

WCF，SOA讲述.ppt

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

Professional WCF 4: Windows Communication Foundation with .NET 4

Pro c# and .NET framework

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

Pro C# 2008 and the NET 3.5 Platform Fourth Edition.pdf

Professional C# 2005 and the.NET 2.0 Platform

Pro VB 2008 and The .NET 3.5 Platform 的配套代码

最新资源

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