SOA filling the Gaps

 Image source: Wikipedia The first part of the trilogy was about the Good Customer . This post is about the Bad Customer. No, the Bad Customer does not shoot the Consultant like Lee Van Cleef  in the picture appearing in the beginning of the post.  The Bad Customer could be The Customer who Knows Everything  or The Self-deprecating Customer  or The Captive  or The Paralyzed Analyzer . What differentiate The Bad from other Customers? Usually,  The Bad Customer does not know what he want to achieve and how he would achieve it. He is not able to define the Consultant's products. The Bad Customer could ask Strategic Consultant to code programs . He may ask a Consultant who is a DBA or an Application Programmer to build an Enterprise Architecture , Infrastructure Architecture or even Business Architecture . He could as well, ask for Strategic consultancy from an ERP Consultant.  The Bad may change the Consultant's assignments, ...

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...