I have purchased and read many SOA books and they have all fallen into one of 2 camps. They are usually either "HOW-TO" implement a SOAP/XML/WSDL based request response guides with the standard buzzwords of SOA Governance, WS-*Everything and the Kitchen Sink*, and of course a vague description of how an Enterprise Service Bus magically does away with years a poorly implemented legacy systems. This is the first SOA book that I have read that did not waste my time with page after page trivial XML examples but actually presented an entire working formal language(extended or inspired by the UML component model I believe) to describe your existing environment("As-Is") and future-state architecture in everday terms understandable by business users and application developers. I'll admit when I read that the approach is both 'Holistic' and 'Anthropomorphic' I felt like I was being marketed some Ginko-Biloba pseudo mysticism but as I read through I understood that this is an approach to SOA, probably the first, to actually make the the underlying services and consolidation of services visible and tanglible in the way an architect builds a scale model of a proposed structure to provide an in depth understanding of the project to those who are unable to turn equations into 3D structures in there heads(which is most of us). The authors crowning achievement, in my opinon, is the realization that everything (Legacy System, Schedule Batch Job, Business Apporval Process, Business Rules, Storage) must be treated as 'Services' is a quantum leap for SOA that moves the concept of SOA from a vague buzzword to a concrete deliverable, tangible item.Click Here to see more reviews about: Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture (Hardcover)
No comments:
Post a Comment