SOA Testing, Validation & Virtualization - iTKO LISA softwar. Implementing Exceptions in SOA. In the ideal world service invocation always completes successfully and returns required results. Unfortunately, in reality, services may and do fail. Such failures can be caused by an array of problems. It can be caused by the service itself, for example validation of the incoming parameters, or just a bug in the service implementation, or by a communication problem, for example, service can not be reached or implementation can not reach underlying database.
Finally, the failure can be caused by a deployment issues, for example, following a software upgrade one of the required libraries is not correctly deployed. A widely adopted mechanism for dealing with failures is exception handling, encompassing both capturing and logging the error and choosing an alternative execution path in the case of failures.
The application is designed as a whole in all of its completeness, including all of the possible exception situations. Figure 1 Islands of exception handling About the Author References. SOA Principles. Listen to the podcasts that accompany this site: Part I - Part II The key to getting the most out of SOA lies within the knowledge of how to create "truly" service-oriented solution logic. That knowledge has been documented as part of the service-orientation design paradigm. As with object-orientation, service-orientation represents a distinct approach to designing solution logic in support of a very specific set of goals. This site introduces the design principles that comprise the service-orientation design paradigm and further explores various aspects and effects of applying service-orientation in the real world.
Becoming proficient with the concepts and principles of service-orientation equips you with an understanding of what is and is not considered "service-oriented" within the world of solution design. Furthermore, this comprehension provides you with a great deal of clarity when surveying the current SOA marketplace. SOA anti-patterns. A lot of emphasis has been placed on implementing Service Oriented Software according to best practices and principles.
But how about the worst practices? In this article, Steve Jones from CapGemini goes over some of the most egregious and thorny antipatterns based on his experiences in the industry and discussions with other SOA thought leaders. The purpose of patterns is to define how systems should be built in repeatable ways; the purpose of anti-patterns is to help you see when that hasn't been done. Format Each anti-pattern presented in this article will follow the following format: Description - What it is? Antipattern: The Shiny Nickel Also know as the "Magpie" Description Used to incorporate the latest technology buzz within your SOA for the sake of telling people about it. Effect SOA projects are characterised by their use of new technologies and their product procurement cycle more than the actual solution being delivered. Cause Resolution Antipattern: The Technology Altar Effects.