Design. Video. Rest. Webservices. Tokyo. SOA in Cardiac Arrest, Long Live Services. Posted on 01/11/09 Blogger Anne Thomas Manes, wrote this excellent post, SOA is Dead; Long Live Services.
This post echos, in a slightly different theme my posts, Amazon Simple Queue Service (Amazon SQS) and also, What is SOA, Really…. A Sacred Omnipotent Acronym. In the Amazon SQS post, I mentioned that it is possible that software companies selling SOA will find they have been “out-serviced” by companies offering services, such as cloud-computing services. Earlier, in SOA – a Scared Omnipotent Acronym, I mentioned how SOA is the art of taking a perfectly good running IT application, breaking it up into its components, and creating a brittle, insecure, unmanageable mess.
Defining SOA as an architectural style. 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.