Despite any declarations made to the contrary, service-oriented architecture (SOA) isn’t dead. In fact, the writer of the original SOA obituary, Anne Thomas Manes of the analyst firm The Butler Group, is scheduled to make a conference keynote address in October announcing the resurgence of SOA.

Many organizations are, however, struggling with services-oriented computing projects where budgets are out of control and positive results are siloed and often infrequent. The problem is that many of those same companies buy into the concept that SOA is a product instead of an architecture. SOA is simply a way of doing things—a comprehensive design pattern. Implemented properly, SOA provides a powerful set of services that can be leveraged within a business process to add efficiency and accuracy to repeatable functions. This article explores characteristics of SOA project failures and how they can be avoided. Assuming that All Technology is Created Equal

Register or login for access to this item and much more

All Digital Insurance content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access