IT is just IT

SOA = given a generic service capability of a service provider the ability to dynamically apply business rules on the generic business processes and the generic information objects to create specific processes and specific objects which are able to respond to the specific service requests from service consumers in a certain context.

SOA is clearly The Next Big Thing, but many companies run the risk of jumping into the approach without looking at where they are leaping. Here is a list of some of the most common pitfalls that could tie a SOA installation into knots.

Take a look at Expect100Continue! When this property is set to true, client requests that use the POST method expect to receive a 100-Continue response from the server to indicate that the client should send the data to be posted. This mechanism allows clients to avoid sending large amounts of data over the network when the server, based on the request headers, intends to reject the request. For example, assume the System.Net.Sockets.ServicePointManager.Expect100Continue property is false. When the request is sent to the server, it includes the data. If after reading the request headers, the server requires authentication and must send a 401 response, the client must resend the data with proper authentication headers. If this property is true, the request headers are sent to the server. If the server has not rejected the request, it sends a 100-Continue response signaling that the data can be transmitted. If, like in the previous example, the server requires authentication, it sends th

The Designing .NET Class Libraries series presents design guidelines for developing classes and components that extend the .NET Framework. The goal of the Designing .NET Class Libraries series is to encourage consistency and predictability in public APIs while enabling Web and cross-language integration. The guidelines presented in Designing .NET Class Libraries are intended to help class library designers understand the trade-offs between different solutions. There might be situations where good library design requires that you violate these design guidelines. Such cases should be rare, however it is important that you provide a solid justification for your decision. You can find the transcripts of the chats related to these presentations in the .NET Framework Chat Transcript Archive. MSDN Gold nugget: Designing .NET Class Libraries

The .NET Framework's managed environment allows developers to improve their programming model to support a wide range of functionality. The goal of the .NET Framework design guidelines is to encourage consistency and predictability in public APIs while enabling Web and cross-language integration. It is strongly recommended that you follow these design guidelines when developing classes and components that extend the .NET Framework. Inconsistent design adversely affects developer productivity. Development tools and add-ins can turn some of these guidelines into de facto prescriptive rules, and reduce the value of nonconforming components. Nonconforming components will function, but not to their full potential. These guidelines are intended to help class library designers understand the trade-offs between different solutions. There might be situations where good library design requires that you violate these design guidelines. Such cases should be rare, and it is important that you p

An interdisciplinary modeling approach for SOA projects The basic concepts of Service-Oriented Architectures (SOAs) and Web services are becoming part of our everyday language and recognized as a suitable architectural style for crafting modern enterprise applications. In this context, the underlying issues of: what makes good services are becoming increasingly critical for ensuring the successful implementation of SOAs. Existing modeling disciplines such as Object-Oriented Analysis and Design (OOAD), Enterprise Architecture (EA) frameworks, and Business Process Modeling (BPM) provide us with high-quality practices that can go a long way in assisting with the identification and definition of appropriate abstractions within an architecture. However, experience shows that these practices fall short when being applied independent of each other. In this article, suitable elements are investigate from OOAD, EA, and BPM. The article also motivates the need for a hybrid approach that combine

The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying Web applications. This IBM® Redbook focuses how the Self-Service and Extended Enterprise business patterns, and the Application Integration pattern, can be used to start implementing solutions using the service-oriented architecture approach. It guides you through the process of selecting and applying Business, Application and Runtime patterns. Next, the platform-specific Product mappings are identified based upon the selected Runtime pattern. The book presents guidelines for applying the Patterns and service-oriented architecture approach to a sample business scenario and for selecting Web services technologies. It provides detailed design, development, and runtime guidelines for several scenarios, including synchronous and asynchronous service buses, UDDI service directory, and the Web Services Gateway. The book concludes with an examination of how a

Back in April 2005, IASA, the International Association of Software Architects, formed a working group focused on IT architectural "Foundations & Taxonomy" with the specific goal of charting the "largely uncharted" profession of IT architecture. One objective of the F&T Workgroup is to locate, qualify, sort, coordinate, and explain resources relevant to IT architects. You can access this Architecture 'Resources' Repository by clicking the following link: http://www.itscout.org/itguide/login.cfm?rdtk=63C7707AB50A91D2607E9E2641CC48D8

A huge demand exists for the development and implementation of SOAs. Learn how SOA can help bridge the gap between business and IT through a set of business-aligned IT services using a set of design principles, patterns, and techniques. This article discusses the highlights of service-oriented modeling and architecture; the key activities that you need for the analysis and design required to build a Service-Oriented Architecture (SOA). The author stresses the importance of addressing the techniques required for the identification, specification and realization of services, their flows and composition, as well as the enterprise-scale components needed to realize and ensure the quality of services required of SOA.

Enterprise Integration Patters This site is dedicated to making the design and implementation of integration solutions easier. The solutions and approaches described here are valid for most integration tools and standards such as IBM WebSphere MQ, TIBCO, Vitria, SeeBeyond, WebMethods, BizTalk, JMS, MSMQ, Web Services etc.

Martin Fowler's Catalog of Patterns of Enterprise Application Architecture A short summary of the patterns in Patterns of Enterprise Application Architecture (P of EAA) .

Development of Further Patterns of Enterprise Application Architecture

Institute For Enterprise Architecture Development

Enterprise Architecture Design and the Integrated Architecture Framework Andrew Macaulay CGEY January 2004 Summary: Describes Capgemini's Integrated Architecture Framework, and describes a model for enterprise architecture and its importance in helping software architects understand the business as a whole. (8 printed pages)