InfoQ Homepage SOA Content on InfoQ
-
Interview: Pete Lacey Criticizes Web Services
Pete Lacey, formerly working with Systinet and now with Burton Group, recently became well-known in the SOA community because of a series of blog posts starting with a very funny one entitled "S stands for Simple". In this interview, Pete talks to InfoQ about the problems he sees with Web services in general, SOAP, WSDL and UDDI, as well as advanced standards from the WS-* family.
-
The Lost Art of Separating Concerns
In a short article, well-known REST proponent Mark Baker claims the default, Web services-based approach to SOA development fails to properly separate concerns, and describes how the more generic interface used in Web architecture leads to an improvement.
-
Interview: Using Agile for SOA
Recently, Digital Focus documented their experience using Agile to tackle SOA for Federal Home Loan Banks. The incremental approach included adopting an SOA platform that could grow as the SOA application portfolio grew, and getting frequent feedback from customers and developers. InfoQ interviewed both the client and the author of the experience report on the project, and business-IT alignment.
-
Incorporating Enterprise Data into SOA
The majority of today's SOA design techniques are centered around definition of services. They use service-oriented decomposition, based on the business processes, enterprise business/functional model, required long term architectural goals and reuse of the existing enterprise functionality. This article takes a more data centric approach...
-
ESB Alternative - Article removed at the author's request
This article was removed from InfoQ at the author's request.
-
SOA Programming Models
Author Boris Lublinksy provides an overview of the dominant programming models that are emerging in the SOA domain including Windows Communication Framework (WCF), Java Business Integration (JBI) and Service Component Architecture(SCA).
-
Using SEDA to Ensure Service Availability
A new strategy for incorporating event driven architecture for scalability and availability of services in the context of SOA. These strategies are based on queuing research pioneered for the use of highly abailable and scalable services, initially in the Web context, but moving into the SOA and Web services context. Actual implementation is described in the context of Mule.
-
Java, .NET, But Why Together?
The Java vs. NET war is over. In this article, Ted Neward looks at how we can leverage the strengths of each together, such as using Microsoft Office to act as a "rich client" to a Java middle-tier service, or building a Windows Presentation Foundation GUI on top of Java POJOs, or even how to execute Java Enterprise/J2EE functionality from within a Windows Workflow host.
-
Eric Newcomer on WS Transaction Standards
In a recent blog post, IONA CTO Eric Newcomer wrote about the OASIS Transaction TC's progress in standardizing the Web services WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity specifications. Eric talked to InfoQ about this particular set of specifications, as well as the standardization process and the role of the big players in general.
-
An Introduction to Web Services Reliable Messaging
Web Services Reliable Messaging 1.1 is available as a new draft version of the OASIS specification originally released by Microsoft, IBM, BEA and others. WS-RM ensures messages can be delivered reliable over unreliable protocols such as HTTP. Paul Fremantle, co-chair of the OASIS technical committee, provides an introduction.
-
Agile Business Rules
James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.
-
Give it a REST: Mark Baker on Web Services
Mark Baker is well-known in the SOA and Web services community because of his continuous efforts to promote REST (REpresentational State Transfer), criticizing many of the standards and specifications as being ignorant of what made and continues to make the Web successful. Stefan Tilkov had the chance to talk to Mark about REST principles, its benefits, and the relationship to Web services.