Because service-oriented architecture (SOA) has emerged as a strategy many organizations are adopting in order to respond more quickly and cost-effectively to customer needs, I really wanted to understand what it was all about.
After reading many articles and talking with a number
of subject matter experts from
Definition of SOA: Service Oriented Architecture (SOA) is a method for breaking down large applications and business processes into smaller “services” and a system for linking them on demand so they can be reused to create new applications and business processes.
While not elegant or profound, this definition helped me understand how SOA
provides organizations with a dynamic infrastructure that allows them to break down large applications and business processes into smaller, loosely-coupled “services” that can be reused to create new applications and respond quickly to customer needs. The result is a simplified, more powerful infrastructure in which services can dynamically scale to meet changing organizational needs or workloads, while reducing cost and management complexity.
With the tremendous value SOA provides also come new challenges. Some of the challenges include managing the complexity of deploying interdependent services, ensuring compliance with multiple service level agreements for the same service, checking for the proliferation of duplicate or overlapping services, and protecting a SOA application and data from unauthorized access to name just a few. Meeting operational goals in a SOA environment requires a new approach.
I’ve enclosed a link to an excellent webcast--Service Management for SOA: Go the Extra Mile—that explores in more detail how Service Management can help tame the complexities of SOA.