ISBN: 0131858580
List Price: $44.99
Amazon Price: $26.99
Usually ships in 24 hours
Buy this book
from amazon.com
or from
amazon.co.uk
|
Avg Cusomer Rating: 5
Reviews:
Summary: Must Read for SOA architects and some Managers/CTOs and CIOs
Depending on your background you need to pick and choose the chapters or sections. I liked the most, the description of the methodology and approach to starting an SOA project. I also liked the focus on architecture with all the components, layers, standars, scenarios, patterns, and solutions. It is the best SOA book I read so far. If you do not like this book, please state what book is better? and for what audience?
What I found missing is a non-vendor biased ROI calculator for an SOA project. But what can you stuff in an 800 pages book? Most CIOs think that reducing cost with hardware and its operations is the only thing to be done, while $9 out of $10 is spent on people, development projects, and training. SOA is the big thing for the next generation of IT where CTOs and CIOs need to focus on in leveraging more optimized business and lowering IT cost.
Summary: SOA for the masses
When I bought this book I took its content quite seriously. I wasn't just reading to learn more about something that might make me sound smarter in some meeting with my boss. I started a project for a client who wanted to build SOA and who was looking at me as someone to 1. explain SOA to them and 2. essentially make it happen. We are three months into this project now and I can honestly state that had it not been for this book, I would have been royally screwed. The book looks like hell because I've gone back and copied and looked things up so many times. My point is that we actually built a lot of our project around how the book proposes SOA should be built and so far the approaches and tips and processes provided by this book have been successful. I've been hearing about SOA for over a year now and I now actually understand it from a 5000 ft perspective and from a low-level technology perspective. I get it and I helped my client get it too.
Depending on who you are, you'll want to concentrate on different parts of this book:
If you're a application designer or architect (or a developer who thinks he's an architect) then almost all of the book will be interesting to you. You can skip the WS tutorials in ch.5+6+7 if you already understand ws-*, but make sure you focus on ch.8-18 and also ch.4. These parts cover SOA and service orientation in detail. I got a lot out of 8. Chapter 18 was the best study of .NET versus J2EE I've ever read and something that I passed along to another client who is struggling with this.
If you're a developer, programmer, or web designer with aspirations of going beyond Flash work, then reading ch.3+6+7+15+17 is a must. Also read ch.5 if you are brand new to web services. Plus, if you have any interest in what's outside of your programming tools on your desktop PC in your cubicle, then read ch.18 to find out out SOA is happening in different platforms.
If you're an analyst-type (data, biz, sys, other) then definitely go through ch.2+3+4+8+9. A lot of the book talks about SOA in relation to business logic encapsulation, SOA and business agility, how SOA brings together business and technology, and so on. This will change the way you document business rules and processes. But most important of all is ch. 11+12. This is where the book establishes a process for service-oriented analysis including a separate process for what it calls service modeling. We completed this part in our project and it proved to be quite the eye-opening approach to deriving services.
Finally, if you are a manager-type or someone who doesn't need to know a lot of the details but still wants to be the one to make the big decisions, then please, please read ch.1+3+4+8+10. Some parts of these chapters may make your eyes glaze over, but skip those and keep moving on. There are key parts that I know will help you "get it" and you really should "get it" before you send your troops to fight the wrong battles.
By the way, you get some chapters for free on the book web site.
Summary: Timely and articulate coverage of all levels of Web services and SOA
W3C defines Web service as "a software system designed to support interoperable machine-to-machine interaction over a network." Web service is based on the three core XML specifications: SOAP, WSDL, and UDDI. These and XML are all evolved from some of the best technologies in the past. For example, SOAP is evolved from RPC and messaging framework and XML is evolved from SGML. Forerunners of web services include but not limited to DCOM, J2EE, CORBA, and CGI scripting.
SOA represents a way in creating a composite computing architecture that defines and drives a vision for what computing should be by using the set of technologies that make up the Web service technology.
Throughout the history of evolution of application architectures, there are some successfully evolved new ones and there are some not so successfully evolved ones. SOA is either becoming a successfully evolved one, or has a great potential of becoming one very soon.
Thomas Erl provides in his book a timely and articulate coverage of all levels of Web services and SOA from the fundamentals, to WS-* Extension, to principles of service-orientation, to phases of software system life cycle, to business process design, and to SOA platforms.
Principle of service-orientation can be used as guidelines for integration strategies for XML and Web services at the application level to the enterprise level. Business process design involves with business automation. As Erl observes in the preface of this book, "service-orientation is concerned with a specific part of the service-oriented world: business automation." An efficient automation process requires, among others, abstracting the essentials from the mass of complex matters consisting of a great variety of nonessentials and, if possible, going straight to the heart of the problem.
Overall Erl's presentation style in the book is lucid and effective in abstracting essentials from complex topics. The diagrams are insightful and illuminating. The case studies are relevant and useful. It can be adopted as a textbook for a university course at the senior level or graduate level in Information Systems such as "Advanced Topics in IT" or in Computer Science such as "Distributed Systems." I am teaching the former in my university by using Erl's earlier book titled "Service-Oriented Architecture A Field Guide to Integrating XML and Web Services" and by incorporating some ideas from this book into my design of the instructional materials. I got very positive feedbacks from students. I definitely intend to add this book to the textbook list when I teach the course again.
Summary:
|
,
amazon.co.uk
,
google.com
