"Released in January 2008 , Mule Galaxy is an open-source, REST-based SOA governance platform that sidesteps the UDDI standard in favor of ATOM. Positioned as the everyman's SOA registry and repository, Mule Galaxy represents a major shift in SOA, toward a more lightweight, open-source approach to service-oriented development. In this talk with Andrew Glover, Galaxy's chief architect Dan Diephouse talks about his own move away from Web services (after creating the XFire project) and Galaxy's RESTful approach to service-oriented architecture."
"Service-oriented architecture (SOA) is an evolution of distributed computing based on the request/reply design paradigm for synchronous and asynchronous applications. An application's business logic or individual functions are modularized and presented as services for consumer/client applications. What's key to these services is their loosely coupled nature; i.e., the service interface is independent of the implementation. Application developers or system integrators can build applications by composing one or more services without knowing the services' underlying implementations. For example, a service can be implemented either in .Net or J2EE, and the application consuming the service can be on a different platform or language."
"Three issues that rise to the top fast when developing a service-oriented architecture are governance, quality, and management. In this article, part of a Network World Data Center series on SOA, learn about 10 tools designed to help you build better apps and spot performance problems before they boil over."
"It is tempting to set ambitious goals and implement a cutting-edge framework that solves all problems. If you have sufficient resources, that is not a bad idea. Generally, developing a framework upfront for your project is considered overhead that fails to provide tangible business value. Starting smaller helps you lower the unforeseen risks, enjoy less development time, lower the learning curve, and get project stakeholders' buy-in. For X18p, I set only two goals based on my past encounters with J2EE code:"
"Instead of becoming a savior, SOA "instead turned into a great failed experiment -- at least for most organizations," Manes said. SOA failed to deliver on promised benefits and after the investment of millions, IT systems are not better than before. In some cases they are worse, with costs higher and projects taking longer, she said."
"This may well be the plight of many CIOs and IT directors today. Companies big and small have invested time, effort, and money over the past few years hoping to realize the SOA (service-oriented architecture) dream. Numerous SOA implementations have resulted in varying degrees of disappointment. And many companies are coming to realize that SOA is more complex to implement than expected, requiring a laser-like focus on all aspects of enterprise data and a deeper shift in organizational culture than any previous technology wave has demanded."
"SAN FRANCISCO (04/30/2008) - Service Component Architecture (SCA), an SOA specification for transforming IT assets into reusable services, was hailed Tuesday as a way to build services with lower barriers to adoption and link SOA to Web 2.0."
"This article will also showcase the advantage of using a flexible and high-performance native XML database management system along with XQuery to enable rapid and evolving loosely-coupled collaborations among trading partners within and across enterprises."
"A service-oriented architecture (SOA) presents a dynamic runtime environment, where loose couplings between service providers and/or service consumers enable powerful and flexible component interactions. Building a communication model to exploit this power and flexibility is a high priority for competitive software development. An event-driven communication model is able to respond better to real-time changes and stimuli than conventional request/reply mechanisms."
"Service-oriented architecture (SOA) and enterprise service bus (ESB) are two buzzwords that have gained significant momentum and traction in live architectures over the last few years. Speaking from firsthand experience, I would say SOA/ESB techniques do deliver increased modularity, flexibility and reusability of components, which has been the age-old promise of object-oriented programming (OOP) and even general software engineering. In particular, SOA/ESB appears to extend effectively on the hallowed OOP principle of encapsulation. But it seems all new paradigms come with a "dark side" that must be effectively recognized and managed to minimize undesirable consequences. What is the dark side of SOA/ESB? This article examines it and proposes a powerful technique and "quasi-architecture" as the solution."
"With their inherent flexibility and vendor neutrality, Web services and the SOA (service-oriented architecture) provide a method by which modern B2B commerce can be implemented in a flexible and economical manner. Web services and the SOA enable more dynamic and cost effective B2B commerce, and this article examines ways in which they make this happen."
"An SOA repository is a mechanism that handles the persistence of distributed SOA data. It is a complex and sophisticated enterprise-grade technology that not only handles persistence and caching, but also enables lifecycle management, security, discovery, and transformation of distributed data from diverse service-oriented applications such as silo applications, Web portals, business processes, and mobile applications."
"Branching out in the SOA space, MuleSource will introduce Tuesday its Mule Galaxy software, an open source SOA governance platform with an integrated registry and repository."
"May 17, 2006—With the industry still buzzing about SOA in general, Oracle and others are now talking about SOA 2.0. Oracle officials talked up this next-generation version of SOA at the JavaOne conference in San Francisco on Wednesday."
"In this article, I will introduce SOA from a Java developer perspective and examine the technologies available in the Java space to build service-oriented applications."
"This article is an attempt to present an approach for transforming service-oriented architecture (SOA) principles from concepts to design and then to code, based on our experiences in the development of our Infosys Radien framework. In this article, we present a systematic requirements-driven approach for designing and building an enterprise application framework for developing applications using the SOA principles."
"To get the sample code working, download the attached XQueryForJavaEnablerForSOASrc.zip file (see the Resources section for sample code), and unzip it to some folder in your local file system. Go to the PathExpressions directory, and type ant run, which will print out the results of the above XQuery into the console, as shown in Figure 1."
"Thus, the combination of business-process modeling tools and SOA enables business analysts to define, configure, change, and optimize the business process with near-zero involvement of the IT staff. This helps organization to respond and adapt quickly to ever-changing business requirements by shrinking the lag between business and IT."
"The web services approach is based on a maturing set of standards that are widely accepted and used. This widespread acceptance makes it possible for clients and services to communicate and understand each other across a wide variety of platforms and across language boundaries. This section briefly describes the protocols and technologies that constitute these web services standards, some of which are mainstays of working on the World Wide Web. In addition to these standards, other web services standards are emerging to meet additional requirements -- especially in the areas of security and management. This section also covers some of these emerging web services standards."
"To get up-to-date on the importance of SOA for Java technology developers, we met with Mark Hapner, Distinguished Engineer at Sun Microsystems, who has served as lead architect of the Java Platform, Enterprise Edition (Java EE, formerly known as J2EE), co-lead of the Enterprise JavaBeans (EJB) specification, and lead for Java Message Service (JMS). He is currently Sun's chief web services strategist. Hapner also helped create Java Business Integration (JBI) and is Sun's board member on the Web Services Interoperability Organization (WS-I)."
"This article presents architectural concepts and language constructs necessary to developing a SOA composite application in Java EE 5. It then presents an example application, deployed in the Java Business Integration (JBI) environment. The example uses HTTP/SOAP binding components and WS-BPEL and Java EE service engines, illustrating how these components can be orchestrated to solve a business problem."
"Pragmatic SOA mandates the reuse—not replacement—of existing implementations, standards, and APIs for minimal disruption to a company's existing IT infrastructure. Fittingly, Fast Infoset causes minimal disruption to existing standards and implementations. No changes or extensions are required to XML 1.0/1.1, SOAP 1.1/1.2, Web Services Description Language 1.1/2.0, and W3C XML Schema. The integration of the Fast Infoset open source implementation into JAX-RPC 1.1.3 as part of the JWSDP 1.6 required no changes to the existing Java-based web service APIs."
"RouteOne was charged with creating a faster, easier, more accessible, and less error-prone system that reduced or eliminated reliance on paperwork, faxing, and phone calls. The company consulted with Sun Microsystems' Sun Services and created a service-oriented architecture (SOA) that linked all parties in a single, seamless chain that enabled them to share relevant information in real time."
"Scalability. Because services in an SOA are loosely coupled, applications that use these services tend to scale easily -- certainly more easily than applications in a more tightly-coupled environment. That's because there are few dependencies between the requesting application and the services it uses. The dependencies between client and service in a tightly-coupled environment are compounded (and the development effort made significantly more complex) as an application that uses these services scales up to handle more users. Services in a web services-based SOA tend to be coarse-grained, document-oriented, and asynchronous. As mentioned earlier, coarse-grained services offer a set of related business functions rather than a single function. For example, a coarse-grained service might handle the processing of a complete purchase order. By comparison, a fine-grained service might handle only one operation in the purchase order process. Again, as mentioned earlier, a document-oriented service accepts a document as input, as opposed to something more granular like a numeric value or Java object. An example of a document-oriented service might be a travel agency service that accepts as input a document that contains travel information for a specific trip request. An asynchronous service performs its processing without forcing the client to wait for the processing to finish. A synchronous service forces the client to wait. The relatively limited interaction required for a client to communicate with a coarse-grained, asynchronous service, especially a service that handles a document such as a purchase order, allows applications that use these services to scale without putting a heavy communication load on the network."
"Thomas Erl describes 7 strategic goals of SOA by guiding listeners through the WhatIsSOA.com Web site. Learn about Intrinsic Interoperability, Federation, Vendor Diversification, Business & Technology Domain Alignment, ROI & Organizational Agility."
"With time and practical experience, however, I realized that although in theory every object has state, behavior, and identity, in practice different object designs use state, behavior, and identity differently. Granted, most object designs I have encountered have had both interesting state and interesting behavior, as predicted by Booch's statement. I call this most common kind of object Service-Oriented. I have often encountered objects, however, that have little or no interesting behavior. These objects, which I call Messengers, are composed primarily of state. On the other hand, I have on occasion encountered objects that have little or no interesting state. These objects, dubbed Flyweights by the Design Patterns book, are composed primarily of behavior. Lastly, some objects are immutable, which means that once their state is established at the beginning of their lifetimes, the state never changes. Although every object does indeed have a unique identity, immutable objects are differentiated more often by value than by identity. For example, two immutable Strings with the value "Hello, world!" do indeed have separate identities -- each one sits at a different address on the heap. But because their values are the same, their identities are irrelevant. It doesn't matter which one you pass to System.out.println."
"Frank Sommers: A key system integration task is to transform the input/output objects, or message formats, of one system to formats understood by another system. An online catalogue might specify a message in a format specific to that catalogue, whereas an online shipping service might require an input in a format that makes sense for that shipper's business."
"In Guideline 1, I said that objects are machines. The kind of machine that service-oriented objects resemble, mathematically speaking at least, is the state machine. A state machine is defined by:"
"You can implement the FastSOA architecture using Java code and relational database technology. However, I found significant performance and scalability problems when testing service bindings created with Java objects and when persisting XML using relational databases. These problems are significant enough that it makes sense to consider alternatives of XQuery, XSLT, and native XML database technology."
"Designing a nimble and effective SOA that can respond to business domain changes and events in a timely manner is a complex task. However, an SOA built around a properly designed POJO layer can help simplify this task. The Geronimo platform provides frameworks and tools that you can use to build a flexible, scalable, and maintainable SOA using POJOs."
"AXIOM (AXIs2 Object Model) is the base for Axis2, where any incoming SOAP message is represented as AXIOM inside Axis2. The advantage of AXIOM over other XML representations is that it is based on a pull parser technique, while most others are based on a push parser technique. The main difference of pull over push is that in the pull technique the invoker has the full control on the parser and he can ask for the next event, where as in the case of push, when we ask the parser to proceed it will fire the events until it reaches the end of the document."
"Service Oriented Architecture (SOA) is a business-centric IT architectural approach that supports integrating your business as linked, repeatable business tasks, or services. With the Smart SOA approach, you can find value at every stage of the SOA continuum, from departmental projects to enterprise-wide initiatives."
"IBM Workplace Forms is an XML-based technology used to gather data from a user much as paper forms are used to gather data. Both the presentation layer and complicated business logic of the form can be embedded in a Workplace Forms document. You use the data gathered by a form to start a business process. It is vital that Workplace Forms can be easily integrated into Service-Oriented Architectures (SOAs). For example, when you use the Business Process Execution Language (BPEL), tasks in a business process are created as Web services. Integrating Workplace Forms into these business processes requires mapping between the data models in the forms and Web services (that is, XForms instances to WSDL and WSDL to XForms instances)."
"You can implement SOA just as well by sending simple messages over Hypertext Transfer Protocol (HTTP). Basically, this is what RESTful Web services do. Representational State Transfer (REST; the name was coined by Roy Fielding) isn't a protocol or technology: It's an architectural style. REST, a lightweight alternative to SOAP, is resource oriented rather than action oriented. It's often summarized as bringing back remote procedure calls to GET, POST, PUT, and DELETE statements using HTTP. In my opinion, this is the second important step."
"So far your columns have been all about session and entity EJBs for services, which is great for directly connected Java applications, like HttpServlets for Web based clients, or Swing applications for rich (we don't like to say "fat") clients. But we have heard that service-oriented architecture is all about loose coupling. Doesn't that imply using SOAP to provide language neutrality and asynchronous protocols that enable the client and server applications to run independently as much as possible? In other words, why haven't you talked much about JMS and message-driven beans?"
"The first article in this series described the basic concepts and role of the Enterprise Service Bus (ESB). This article focuses on describing scenarios and issues for ESB deployment to support a Service-Oriented Architecture (SOA). One or more of these scenarios might apply to the SOA and ESB needs of your organization."
"The following statement may shock you, given that I am the EJB Advocate -- but just because you can code everything on the server side in Java using EJB components doesn't mean that you should. My take is that we are seeing a natural evolution of technology on the sever side similar to that which we saw with Java? servlets on the client side."
"State-of-the-art IT integration is the implementation of Service-Oriented Architectures (SOAs) using Web services technologies, and many excellent descriptions of their benefits and practice are available (see Resources). More recently, the concept of an Enterprise Service Bus (ESB) has been expressed as a key component of the SOA infrastructure (see Resources). However, it is important to clarify whether the ESB is a product, technology, standard, or something else. In particular, is the ESB something that can be built today, and if so, how?"
"Applying SOA concepts to the user interfaces and delegating common software life cycle functions to a UI container using the portal/portlet architecture can improve time-to-value for a software developer. The WSRP standard, delivering UI components through Web services, offers advantages to both the content provider and the content consumer, enabling a type of application aggregation without programming. Portal frameworks can aggregate portlets into a user interface in a dynamic manner. The participation of users in the SOA can be modelled as a Web service, with human interactions facilitated by the Human Task Manager."
"This briefing provides a technical, practical overview of SOA reuse & connectivity offerings, including the benefits and importance of an ESB in creating and maintaining a flexible IT infrastructure."
"Over the last four decades, software architectures have attempted to deal with increasing levels of software complexity. But the level of complexity continues to increase, and traditional architectures seem to be reaching the limit of their ability to deal with the problem. At the same time, traditional needs of IT organizations persist; the need to respond quickly to new requirements of the business, the need to continually reduce the cost of IT to the business, and the ability to absorb and integrate new business partners and new customer sets, to name a few. As an industry, we have gone through multiple computing architectures designed to allow fully distributed processing, programming languages designed to run on any platform, greatly reducing implementation schedules, and a myriad of connectivity products designed to allow better and faster integration of applications. However, the complete solution continues to elude us. Now Service Oriented Architecture (SOA) is being promoted in the industry as the next evolutionary step in software architecture to help IT organizations meet their ever more complex set of challenges. Is it real, though, and even if it can be outlined and described, can it really be implemented? The thesis of this paper is that the promise of SOA is true; that after all the hype has subsided, and all the inflated expectations have returned to reality, you will find that a SOA, at least for now, is the best foundation upon which an IT organization can take its existing assets into the future as well as build its new application systems. This is the first in a series of papers intended to help you better understand the value of a SOA, and to develop a realistic plan for evaluating your current infrastructure and migrating it to a true service-oriented architecture."
"Virtualization of business functions, a key goal of an SOA, is achieved by isolating service definition and usage from service implementation. Services may be implemented using a wide range of technologies, including IBM WebSphere® MQ, IBM CICS® or IBM IMS?, Java? 2 Platform, Enterprise Edition (J2EE) Enterprise JavaBeans (EJB), Java classes, IBM DB2® Queries, Java Message Services (JMS), or Microsoft® .NET. Service requesters dispatch requests to a service provider that offers the capabilities they desire, unaware of its implementation."
"Although the use of XMLBeans doesn't require an application server, you can leverage XMLBeans in Java 2 Platform, Enterprise Edition (J2EE) applications deployed in any application server, including Geronimo. This article explains the high-level concepts and shows some pseudo-code that illustrates how to do this. However, you should follow through using actual files to get the maximum benefit."
"Jenny Ang is a Consulting IT Architect with the Enterprise Architecture and Technology Center of Excellence, IBM Global Services US. She has in-depth knowledge of all phases of the software development life cycle applying object-oriented methods and techniques. As a solution and application architect, she is currently focused on service-oriented architectures, Web services and Web-based development projects which exploit J2EE technologies. She holds a Bachelor of Engineering degree in Civil and Structural Engineering and a post-graduate diploma in Systems Analysis from the National University of Singapore."
"A huge demand exists for the development and implementation of SOAs. So if SOA is not just about the products and standards that help realize it, for example through Web services, then what additional elements do you need to realize a SOA? Service-oriented modeling requires additional activities and artifacts that are not found in traditional object-oriented analysis and design (OOAD). The article “Elements of Service-oriented Analysis and Design" describes an initial set of reasons why you need more than OOAD. It also describes how business process management or enterprise architecture (EA) and OOAD are inadequate means of conducting analysis and design. Also, in the IBM Redbook entitled “Patterns: Service-Oriented Architecture and Web Services", I illustrate the major activities of this service-oriented modeling approach."
"Kishore Channabasavaiah received a Bachelors degree in Mechanical Engineering from Bangalore University, India. He is currently an Executive Architect in the Chicago Innovation Center of IBM Global Services. He provides thought leadership for e-business Integration solutions with a focus on Web services and end-to-end solutions. His current focus is in Web application solutions, conducting technical solution reviews, Web services, service-oriented architecture, and Pervasive Computing. You can contact Kishore at kishorec at us.ibm.com."
"The briefing begins with an overview of the service management lifecycle, and continues with a detailed discussion of the implementation and management of a Service-Oriented Architecture (SOA) solution. It steps through the use of IBM's world-class Rational® and WebSphere® tools for defining, modeling, and implementing new services and managing those services throughout their lifecycle. It also discusses SOA quality management and governance throughout the service lifecycle. The briefing closes with a review of SOA best practices, resources, and calls to action."
"Continuing our series on architecting an Enterprise Service Bus (ESB) for a Service-Oriented Architecture (SOA), I now take a look at the various apparent solution patterns to the scenarios described in Part 2 (see Resources)."
"Web services promote an environment for systems that is loosely coupled and interoperable. Many of the concepts for Web services come from a conceptual architecture called service-oriented architecture (SOA). SOA configures entities (services, registries, contracts, and proxies) to maximize loose coupling and reuse. This material, describes these entities and their configuration in an abstract way. Although you will probably use Web services to implement your service-oriented architecture, this chapter explains SOA without much mention of a particular implementation technology. This is done so that in subsequent chapters, you can see the areas in which Web services achieve some aspects of a true SOA and other areas in which Web services fall short. Although Web services are a good start toward service-oriented architecture, this chapter will discuss what a fully implemented SOA entails. We will examine the following issues:"
"With the introduction of Web Services over the last year or so, there has been a renewed interest in service-oriented architecture (SOA). An SOA is an architecture that has special properties. It is an architecture made up of components and interconnections that stress interoperability and location transparency. The term service has been used for more than two decades. For example, leading transaction monitoring software has used the term "service" in the early 1990s. Many client-server development efforts in the 90s used the term "service" to indicate the ability to make a remote method call. Web Services has given the term service more prominence in the last few months. Services and service-oriented architectures are really about designing and building systems using heterogeneous network addressable software components. In this article, I will explore the evolution of SOA, make a case for SOA, and describe some of the properties of SOA."
"An architectural approach to SOA leverages high-level business requirements that help to ensure that each solution meets the organization's business needs. To bridge the often sizable gap between the needs of the business and the realities of design (and their respective languages), SOA enables an abstracted approach that provides clear definitions at every stage of specification and development. This, in turn, facilitates agility."
"A service-oriented architecture is one that has a robust service layer. The services in the service layer have the ability to be invoked over a network. The technologies used to invoke the interface of the services stress interoperability. The services in the service layer also stress location transparency so they may be discovered and used dynamically. Most companies have already built components with many of these properties. They are some of the things to keep in mind when designing services or harvesting existing components to be service-enabled. Services can be built using a large number of technologies from application servers like .NET or J2EE, middleware solutions, or even adapters for database systems that enable access to data via Web services. In this article, I will provide some additional details on the properties of a service and how those properties are satisfied by Web services."
"Several architecture and design decisions are essential for SOA to meet its stated goals and benefits. The SOA architectural decisions generally relate to the choice of technologies and products necessary to meet the quality of service attributes required of a business process. Design choices focus on choices that must be made about services using the technique described later on service-oriented analysis and design. Some of the key decisions are:"
"We invite you to participate in The Event Web Community, a not-for-profit community organization where you can search, discover, and share information about the event web. Please visit Spy-Dir-Web.com for more details."
"Another important part of the "instruction manual" is SOA governance. As you can imagine, with myriad web services available for reuse throughout the infrastructure, there is a greater need for SOA governance. While IT has always upheld a semblance of governance to oversee the entire infrastructure's IT processes, the level of rigor and detail around governance varies from company to company. However, governance is becoming increasingly more important as SOA is rolled out throughout the company. And with a growing emphasis on governance comes a focus on quality management within the SOA."
"Traditional uses of analytical tools tend to focus on output that will be presented to a human for interpretation. The purpose of the SEAI concept is to provide a mechanism to use the multi-dimensional analysis features of best-of-breed analytical tools to create automated responses in terms of existing system attributes and operations. The SEAI component is designed from the ground-up to be an Event-Driven Architecture (EDA), which makes it easy to use its services in enterprise SOA ecosystems to connect them in a loosely coupled asynchronous manner. Taken as a whole, these concepts allow:"
"The enormous amount of activity surrounding service oriented architectures over the past few weeks has moved the adoption needle more than any previous comparable amount of time. The ecosystem for SOA is rapidly growing with each passing day as application providers deliver SOA-enabled applications and as more and more customers take steps to adopt an SOA in order to become on demand businesses that integrate business processes and technology."
"In this work, I shall discuss the various aspects of testing a web service in a service-oriented architecture. I shall stress upon the musts in testing the web service, the interoperability of web services, and quality of service and recovery in case of a service disruption. I shall conclude with mentioning some of the best practices in SOA."
"This article will show you how the two concepts of Component Architecture and Service Oriented Architectures (SOA) might fit together within an environment without having to decommission all the work done using the principles of component architecture. The premise of SOA is to not have developers adopt a rip and replace philosophy to upgrade mission critical systems but to make those systems more accessible to business users and make them easier to maintain."
"So, if you've been hesitant to initiate an SOA project this year, make it your New Year's resolution to better align your technology with the needs of the business and join the legions of developers driving revenue up and cost out of their companies. Follow these ten steps and you'll be on your way to success."
"A service-oriented architecture has services that developers create in a service layer. The services that they develop have published interfaces. These interfaces support a distinct business domain. Organizations that focus their development effort around the creation of services, will realize many benefits. The most common scenario for development organizations is to have some experience with component-based development. The use of application servers such as J2EE or .NET for hosting applications is becoming more common. If your organization is using component-based development practices and application servers for business logic, then you are already service-oriented. By following the service-oriented mind set with even more rigor, combined with the component-based approach to software development, your organization will realize many benefits."
"Sandy Carter, Vice President, SOA Strategy, Channels and Marketing, IBM was kind enough to talk to Developer.com and Gamelan.com about how BPM (Business Process Management) fits into an SOA (Service Oriented Architecture) Strategy."
"Service Oriented Architecture (SOA) is another strategic milestone in the enterprise architecture world. Many enterprises fuel the myth that surmount the today's SOA mantra. Is it real or hypothetic? Are CTOs and CIOs responsible for this hype? The questions remain unanswered. Most of the time, one does not look past his previous attempts towards the solutions he delivered and learn from his drawbacks. Enterprises bet on SOA, but how do you implement a successful SOA today in your company? There are some adhoc SOA implementations available; they may not potentially transform the way IT and businesses colloborate. But, do these implementations reap the real benefits of a SOA? This is just a question of time."
"For some time now, the existence of Web services technologies has stimulated the discussion of Services-Oriented Architectures (SOAs). The discussion isn't a new one; the concept has been developing for more than a decade now, ever since CORBA extended the promise of integrating applications on disparate heterogeneous platforms. Problems integrating those applications have always arisen, often because so many different (and non-CORBA-compliant) object models became popular; thus many architects and engineers became so bogged down in solving technology problems that the promise of developing a more robust architecture that would allow simple, fast, and secure integration of systems and applications was lost. The problems, however, persist, and become more complex every year. Basic business needs such as lowering costs, reducing cycle times, integration across the enterprise, B2B and B2C integration, greater ROI, creating an adaptive and responsive business model, and so on keep us looking for better solutions; but more and more, we are finding that "point solutions" won't solve the basic problem. The problem, in many cases, is the lack of a consistent architectural framework within which applications can be rapidly developed, integrated, and reused. More importantly, we need an architectural framework that allows the assembly of components and services for the rapid, and even dynamic, delivery of solutions. Many papers have been written about why particular technologies such as Web services are good, but what is needed is an architectural view unconstrained by technology. Let's begin by considering some of the fundamental problems that underlie our search for a better foundation, for how these problems are addressed will determine the success or failure of the effort."
"Service-Oriented Architecture (SOA) is an emerging technology. But it has not yet fully emerged out of the academic and research-labs closets. The book under review is the first accessible introduction to Service-Oriented Architecture (SOA) and brings the technology a step closer to limelight."
"If, on the other hand, you share in the pain of upgrading, maintaining and enhancing existing applications, the read on. Having gone down the road of applying SOA to existing apps a few times, I'll try to pass on where some of the potholes are, so you can avoid joining me at the bottom of them."
"Service Oriented Architecture (SOA) was one of the emerging buzz-phrases of 2003. This article provides you with a quick look at the principles behind SOA and the benefits it gives you so you can begin an analysis of whether or not SOA is in your future."
