The key to a successful SOA implementation
It is widely known that Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. In general, entities (people and organizations) create capabilities to solve or support a solution for the everyday problems they face in the course of their business. It is therefore natural to think of one person’s needs being met by someone else. In the world of distributed computing, one computer agent’s requirement may be met by a computer agent belonging to a different owner.
Service Oriented Architecture and Event Driven Architecture (EDA) are the proclamation of the moment, but how many implementations have really succeeded beyond application integration or point-to-point connection between partners or application development? What really is SOA and EDA, and how can it be implemented easily and efficiently? These are some of the many problems IT architects repeatedly face.
Services Today
Organizations across all industries sectors are planning an SOA program with the main focus being to develop an SOA solution that fits their own bespoke requirements. These types of implementations up until now have focused on application development making use of services technology, namely web services. Due to this approach, the level of reusability of the services becomes very limited reducing the benefits promised by the SOA.
Limited service lifecycle management removes the capability of engineering better services bringing back the ‘application spaghetti model’. Many of these implementations are IT driven and not business driven leaving the service without a business domain or ownership.
 | to download the SOA Accelerator Datasheet |
|---|