Rating: 
Summary: OK as a nontechnical overview, although with flaws
Review: An OK overview, not too much hype. However, the explanations are often so brief that the more complex standards (BPEL4WS being a particular case) would be impossible to understand if I hadn't read the official documents. The figures are plentiful and often awful. Many have little connection to the text that references them (13.2, 15.1, 15.2 being good examples). Entities in the figures are not explained in the text, and the text uses terms that do not show up in the figures. Also, anyone who includes a six-page listing of XML syntax without any kind of structuring, enhancement, or occasional word of explanation (e.g., listing 12.1) should be pilloried. Despite the fact that this has become some sort of sport, XML syntax was not designed to be read by humans in great quantities.The style was a bit too chummy for my taste but perhaps that is what makes the books acceptable to nontechnical people? And the author should really find another favorite verb instead of "leverage". He employs it instead of "use", "implement", "incorporate", "include", and some more words, all of which would be either shorter or more clear (I thought I even spotted a couple of cases where "provide" seemed intended). By page 200 it gets to be a major irritation.
Rating: 
Summary: Worth the Money
Review: I found the information in this book perfect for me, a project manager. This was the first book on EAI that I've purchased, and I found the subject matter clear, concise (where needed), and presented in a logical order. I thought the illustrations were helpful, and easy to understand. This is a very complex topic, but this book does a good job in clearing things up. I'm a consultant, and reading this will help me serve my clients implementing application integration solutions. Best 40 bucks I've spent in a while.
Rating: 
Summary: Extremely disappointing
Review: I found this book to be very short on any kind of meat or details. I'm very tempted to ask for my money back. There is no insight here - the book could have been compiled from a series of press releases. I think the standard of the book is typified by the 'bibliography' which seems to list every single article the author has ever written, including in magazines like Computer Shopper a decade ago. How that is supposed to be any help to anybody I cannot see. Do yourself a favor and skip this one.
Rating:
Summary: Current, and To the Point
Review: I really enjoyed this book; it seemed to answer all of the questions I had about application integration. I also enjoyed the way this book is organized, it gets right to the point, gives you the skinny, and moves on to other topics. However, you should know that this is a strategic book; there is not much here for hardcore developers. However, I be a manager.
Rating:
Summary: Could have been better, but not much better¿
Review: I've been following the author for a while, reading both his articles and books. I like his practical approach to hyped technology, such as Web services. Unlike the other books that portray Web services as mandatory, and always right for whatever you're doing, the author points out the fit, as well as the weaknesses. Refreshing. It would have been nice to see more implementation details, but I was not disappointed with this book.
Rating:
Summary: EAI+Web Services = This Book
Review: I've read the author's other books and found them very valuable, and this book is no different. This book does a great job in explaining how Web services fits into the world of EAI. I really liked the way the author approaches the topic, using practical applications and examples, where to use Web services, and where not to use Web services. Good information beyond the hype. However, this is not just a Web services book. You'll find most of the information you'll need to run an EAI project (don?t ask me how I know that). The book does not dictate a static solutions, as do other Web service books, but allows you to find the right technology for the needs of your project.
Rating: 
Summary: To each his own
Review: Like Linthicums previous books, this is surely not for someone who wants to get technical folks, its for the business people. As such, if you are a technical person and occasionally need to advice the management or help them understand technical issues, this book might help to understand their framework. If you see it on your bosses or customers bookshelf, at least skim through it in the local bookstore. Otherwise, if unlucky, you might be forced to look at the pictures anyhow in the next management meeting shown in power point titled "Road Map" without a good counter-argument prepared.
Rating:
Summary: Good overview of EAI
Review: Linthicum gives a good overview of integration approaches and middleware technologies. Makes sense of all the options out there.
Rating:
Summary: Good overview of EAI
Review: Linthicum gives a good overview of integration approaches and middleware technologies. Makes sense of all the options out there.
Rating:
Summary: Text for Technology & Project Managers
Review: Linthicum writes a comprehensive text for technology managers. The 500-page book describes the world of EAI in detail with an emphasis on web services. It covers the benefits and limitations of web services, provides examples of where to use and not use them, and introduces standards with an emphasis on XML. The book encourages IT to make the much-needed shift from an information to a service-orientation. As such, a considerable part of the book dedicated to emerging EAI styles, such as SOA (Service Oriented Architecture), which requires IT to think in business terms and promises to speed development and decrease integration time when correctly implemented. Coders and those looking for technical information on standards should look elsewhere. The book contains many diagrams that are crude but effective. The writing style is unrefined and repetitive. This can be overlooked if you're willing to skim through them.
| 
