• English
  • Nederlands
HOME
SEARCH
CONTACT
NEWSLETTER
 
 
 
CONTENT
About us
Call for contribution
Contributions
The CIO talks
Proceedings
Blogs
Master thesis
Forum
Wiki
Events calendar
Links
Login/Register
advertisements
Zoek je een baan?
Zoek je hulp?
Zoek je een opleiding?
Zoek je een boek?
Zoek je een tool?












 
 
BLOGS
SOA, the hidden benefits
Adrian Grigoriu   
Friday, 08 February 2008

Agility and technology reuse are the major benefits associated to SOA. The reality is that SOA, frequently approached outside an Enterprise Architecture context, is developed incrementally, without the benefit of the big picture the Enterprise Architecture delivers. As a consequence, the promised agility is achieved late, towards the end of the SOAisation of your Enterprise when technology reuse may require costly redesign.

It is worth mentioning though that Business process reuse rather than IT is the advantage since SOA identifies similar business activities and groups them in a service. SOA reduces process replication and then the application de-duplication. Nonetheless, there are a few other major SOA benefits which should be more easily achieved, understood and accepted. Invoking these advantages would make SOA a joyous sell rather than the reported stressing experience.

1. Business service accountability, improving business and IT governance.

Applications and suites, usually a bundle of many functions, provide many services; in practice, a large group of business and IT people will share the responsibilities for the data and behavior of applications. But who can hold accountable such a group of individuals with many other responsibilities? Neither the stick nor the carrot would work in such an environment where neither accountability or authority can be assumed. On the other hand, for a SOA business service, there is a specific function or group assigned responsibility: it does not matter it is an IT or business issue, there is one single point of contact which will assume blame or praise.

2. IT technology virtualisation behind SOA business services, reducing the Business and IT divide and enabling audit for a regulatory compliant architecture.

This a major achievement since your applications and technology are hidden behind IT services with contract interfaces supplied to the business. From a business perspective this is what really counts. IT becomes a service provider offering business services at a QoS secured by an SLA, well comprehended, quantified and eventually paid for by the business. No more blame culture. The separation of concerns pacifies the parties with no more business and IT divide as an additional advantage. The access is logged as well for various reasons such as regulatory.

3. Untangling the applications providing a clean architecture, reducing the side effects of change.

There is no more random access to parts of applications or databases which makes any change a burden and any modification of an application a major risk because of unforseeable effects.

4. Extended lifetime for your legacy applications, reducing the immediate pressure to replace them.

Although there are other increasing costs related to legacy technology, there is no more pressure to replace it; you can do it at your own convenience when a viable alternative exists. This is an extension of the technology virtualisation.

 






Comments (1)
RSS comments
Written by Lydia Duijvestijn on 16-03-2008 18:39
 
 
Hi Adrian, 
 
I hope you forgive me if I am a little sceptical about the ease of achieving the 4 hidden benefits that you just sketched. In my view these benefits can only be realised with the right amount of governance and discipline and when responsibilities and service levels are clearly defined and taken care of.  
 
Let's start with 3 and 4. I fully agree with you that (3) untangling applications leads to more modularity and structure and that data encapsulation is the way to avoid corruption of company data. I also agree with you that (4) legacy application wrapping extends the lifetime of your legacy applications. Both techniques can lead to serious performance impacts if not done properly. I don't agree with you that they are specific SOA benefits. These benefits were also listed by the advocates of object orientation in the 80s. By the way both data encapsulation and legacy wrapping can lead to serious performance problems if not done properly. 
 
Now 1. and 2. (1) Business service accountability could be a great benefit, but I see a couple of "monkeys and bears" (sorry for the Denglish) regarding composite services. Is the owner of the composition also accountable for the subservices? Does he own all the SLAs? Who owns the IT that supports the services? What if the IT is outsourced? What if there are multiple providers? 
 
(2) IT virtualisation is probably the real benefit of SOA if properly implemented. But again, the IT will only become invisible and unnoticed when all processes and SLAs around it are smoothly organised. I don't think that that will be any different in a SOA environment from a more traditional environment. 
 
Hope I haven't been too critical on you, but I thought you also deserved a reaction...take care!

 

Only registered users can write comments.
Please login or register.




Share / deel
Del.icio.us!Google!Technorati!Yahoo!
 

Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not permitted. Readers are requested to notify This e-mail address is being protected from spam bots, you need JavaScript enabled to view it of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.
feed image
ISSN: 1877-2994