SOA filling the Gaps

Ten years ago Reuse was the promise of SOA . Almost 15 to 20 years ago Reuse was described as main benefit of Object Oriented .  SOA Reuse is Easy to say and hard to do . 100% Reuse was an unrealistic target. However, even 30% Reuse ratio could provide significant Business Value.  There are Systems or Systems Components, which you can not break into Services reasonably, e.g. Batch Systems or Legacy Systems . People tend to ignore systems that do not fit well to the Service Oriented Architecture due to lack of Reuse or insignificant Reuse. They should not . Instead of ignoring them by fitting them into  Services Framework and Architecture, they should accept the reality, that building Services for these Systems is wrong.  Douglas Adams's Last Chance to see Douglas Adams 's most famous book are  The  Hitchhiker's Guide to the Galaxy  book.  However, Adams's favorite book was: Last Chance to see  which was written together with Mark...

image source: Wikipedia The Self -deprecating Customer is exactly the opposite type of The Customer who Knows Everything . He automatically accepts the Consultant advice, without any questions or hesitations. Probably, you will not believe that the first example of a  Self -deprecating Customer I think of, is the CIA . It is about a project named Triangle. Triangle was an Information Technology project of Legacy Modernization and systems expansion after September 11 attacks .  After  completing the Development phase, the CIA begun the Implementation phase. However, someone who was a Senior Manager, thought that it will be a good idea to rethink if the project fulfills its goals. A committee of 100 leading academic and IT industry experts, investigated the project. The main recommendation in  the  committee' s detailed report was: stop implementation and fix the errors in the systems. Afterwards the systems could be implemented again. It shou...

One of the most difficult tasks of a major paradigm shift or architectural change or major technological change is Organizational Culture change (Corporate Culture change). Without a cultural change SOA 's Value Proposition could be turned to nothing, because SOA's benefits such as Service Reuse will not take place.  In a recent ebizQ webinar Gartner 's VP Distinguished Analyst Yefim Natis , talked about SOA Proponents’ Myths. 100% Service Reuse is one of these myths. The reality is that successful Service Reuse ratio is about 30%. It is obvious that Service Reuse is easy to say and is hard to use . The expectations of near to 100 percent usage of Objects in Objects Oriented also failed. However, there are significant measured benefits even to small percentage of Object Reuse and more significant benefits for small percentage of Service Reuse. Why is Service Reuse limited? The main reasons are Technical and Cultural. As far as Technical reasons are concerned, somet...

Reuse is often cited as a major SOA benefit and justification. It is easy to explain and to understand Reuse Value Proposition in IT and Business perspectives. Services and Processes Reuse reduces Maintenance & Development costs, enable shorter Time to Market and is a key for building applications through assembly of existing Services by non-IT employees as mentioned in my first Web 2.0 for Dummies post . Understanding, Reuse Value Proposition is not enough for realizing the benefits. A SOA initiative without Reuse or with a low Reuse Ratio is doomed to failure. According to many analysts' reports, NIH is a consideration of some software products they analyze. NIH, stands for Not Invented Here. As most of the analyst firms' headquarters are in the largest market i.e. USA , it stands for software products build by companies in other parts of the globe. For example, Fujitsu 's excellent BPM suite invented in Japan or many years ago Dynasty one o...