Enterprise Architecture and Integration: Methods, Implementation and Technologies

"What's in a name?" -W. Shakespeare It's like being hit by a bus; this book is a serious read. I had to read it twice to simply understand the reasoning behind the title "Enterprise Architecture and Integration". This is not a typical technical book. It is a collection of concepts, statistics, challenges and solutions packed in only about 360 pages, but after you are done reading it you feel like you just finished reading Leo Tolstoy's war and peace. Only after reading the whole book, you will realize that sum of the pieces, and the knowledge acquired throughout the book, is what will make you start appreciating the book, and its value; which is the product of collaboration between the authors of each chapter, and the hard work by Wing Lam to put it together. Of course there were some questions in my mind, such as to why they thought it was important to talk about RFID, specifically in the last chapter of the last section Hmmmmm, also why the "Architects" didn't see the downfall of the SOA and it's shortcomings including its inability to deliver on ROI. I am a firm believer that architectural books should not be bound by time and space but represent concepts, ideas creations that are applicable regardless, so therefore I suggest that the title be changed to "Making of an Enterprise Architect and an Integrator", which I believe what this book intends on delivering. And to answer Mr. Shakespeare's question I simply say: Everything. Best Fishes and thank you for reading.