SOA antipatterns

When the SOA paradigm breaks

From the developerWorks archives

Gary Farrow

Date archived: May 14, 2019 | First published: June 09, 2009

Service-Oriented Architecture (SOA) is the de-facto architectural approach for many IT initiatives. It is therefore important to understand the circumstances where this paradigm breaks, as this can significantly impact the delivery of IT programs. This article highlights two SOA antipatterns that define problems that can occur in the execution of SOA deliveries. A simple frame of reference for SOA is first introduced in the form of a layered reference architecture. The reference architecture is then used to illustrate the underlying reasons for the occurrence of the antipatterns. For each antipattern a description is provided that highlights the root causes of the problem and the approaches to re-factoring the solution, hence facilitating successful delivery.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

Zone=Web development
ArticleTitle=SOA antipatterns