Regular marked price: $59.95Discount Price: $37.77
Cost Savings: $22.18 (37%)Price fluctuation possible.
How soon does it ship: Normal ship time within one day
Shipping? Absolutely FREE if you qualify for Super Saver Shipping.
Type of bind: Hardcover
Dewey Decimal Number: 004.068
EAN num: 9780471768944
ISBN number: 0471768944
Label: Wiley
Manufacturer: Wiley
Quantity: 1
Page Count: 384
Printing Date: April 28, 2006
Publishing house: Wiley
Sale Popularity Level: 202617
Studio: Wiley
Other books you might be interested in perusing:
Editor's Notes and Comments:
Product Description:
Praise for Service-Oriented Architecture
'This book provides a superb overview of the SOA topic. Marks and Bell provide practical guidance across the entire SOA life cycle-from business imperatives and motivations to the post-deployment business and technical metrics to consider. With this book, Marks and Bell demonstrate a unique ability to take the complex dynamics of SOA, and through an eloquent set of metaphors, models, and principles, provide an understandable and insightful how-to manual for both technical and business executives. This will become a required handbook for any organization implementing SOA.'
—Dan Bertrand, Enterprise Technology Officer & EDS Fellow, EDS Corporation
'A fundamental breakthrough in the business and technology perspectives of SOA-this book belongs in every software developer, architect, and IT executive library. Marks and Bell demonstrate a creative and practical approach to building complex, service-oriented systems. I especially liked the hands-on perspective brought to multiple aspects of SOA. A must-have guide in the technology turbulence of the future.'
—Ariel Aloni, Chief Technology Officer, SunGard Data Management Solutions
'This outstanding text gets straight to the heart of the matter, cutting through the hyperbole and discussing how to drive real business value through SOA. It will certainly impact my behavior, our governance models, and, subsequently, the successful business outcomes we derive as we continue to embrace SOA. A must-read for battle-scarred SOA veterans and fledgling architects alike.'
—Christopher Crowhurst, Vice President and Chief Architect, Thomson Learning
'Too often, SOA has been perceived as 'all about the technology'-standards, technology stacks, operational monitoring, and the like. In this book, Marks and Bell expand beyond the technology to provide a refreshing business-driven perspective to SOA, connecting the dots between business requirements, architecture, and development and operations, and overlaying these perspectives with tried-and-true governance techniques to keep SOA initiatives on track. A must-read for those leading the charge to adopt SOA within their enterprise.'
—Brent Carlson, Chief Technology Officer, LogicLibrary and coauthor of San Francisco Design Patterns: Blueprints for Business Software
'Marks and Bell have captured a wealth of practical experience and lessons learned in what has become the hottest topic in software development. In this book, they explain in detail what works and what does not, from procedural issues to technical challenges. This book is an invaluable reference for organizations seeking the benefits of SOAs.'
—Dr. Jeffrey S. Poulin, System Architect, Lockheed Martin and author of Measuring Software Reuse: Principles, Practices, and Economic Models
'One of the last things companies often consider when implementing a business solution such as SOA is the impact on people. Marks and Bell provide an in-depth look at 'what has to change' from a process standpoint to make any SOA implementation a success. A great read for those considering to embark on an enterprise SOA and looking for the right mix of people, process, and products.'
—Alan Himler, Vice President of Product Management and Marketing, LogicLibrary
SOA is a complex topic and a complex organizational goal
Service-Oriented Architecture: A Planning and Implementation Guide for Business and Technology shows you how to plan, implement, and achieve SOA value through its prescriptive approach, joining the business and strategic perspective to the technical and architectural perspective.
Applicable to all industries, technology platforms, and operating environments, this innovative book provides you with the essential strategies to drive greater value from your SOA and realize your business goals.
User popularity level:
Rated by buyers 
-
The book is a decent entry point into the somewhat muddled world of SOA. I rate it a 1 star, however, because the book is heavy on marketing hype and light on details/content. I bought this book primarily because it had consistent high ratings from other reviewers, but I think it's likely that these reviewers are fake, just propping up the rating (if you look at most of the 5 star reviewers, they only rate one book - this one).
The book paints SOA as the ultimate enterprise IT panacea. The solution to all of your business problems. SOA of course can ameliorate some of the tangle of entprise architecture, but I believe, as Fred Brooks said, "there's no silver bullet".
For example, take this statement:
"Although nearly every business and IT executive for the last 30 years has wistfully dreamed of achieving business agility, there has been little real progress toward that end save for a few exceptional firms. For most organizations, business agility is a vision without reality. Until now. SOA and services provide a means to achieving true business agility."
Obviously this is massive hyperbole. There have of course been a myriad of improvements in business agility in the past 30 years, some big, some small. Take the PC, the internet, the web, oo, uml, automated testing, open source, faster hardware, etc. These have all helped businesses build software faster, cheaper, better. The problem is that complexity has out-paced us, not that SOA is filling a void of improvements.
They buttress these sweeping statements with numbers, but those too seem a bit groundless (at least I saw no footnotes to back these up). For example:
"Imagine you can launch new products and services 30% faster than your competitors because you eliminated friction within your enterprise..."
...or...
"The time to implement needed system changes to support these new products has been cut by 25%..."
Further, the book is also quite redundant and obvious. Take chapter 2 - section: "SOA is all about Services". First sentence:
"Service-oriented architecture is nothing without services."
Probably true, but it's a bit like like saying "Object Oriented Design is nothing without objects". Next sentence:
"Services are the primary asset of SOA".
Two sentences later:
"The fundamental unit of an SOA is a service."
3 sentences later:
"An SOA with services is useless unless those available services actually are consumed."
Sure, but any system is useless unless there are users or consumers. And finally, to sum up the section, they end on:
"But why are services so important to an SOA? ..."
Anyway, I'm sorry to bash this book so hard, but I felt compelled to write this review because (a) the book is pretty light on content and (b) I feel like there is some duplicity in all these positive reviews...and if that's the case, it's disappointing.
Rated by buyers 
-
This book is an excellent SOA technological introduction that presents major architectural concerns that most architects, team leads, developers, and software modelers struggle with. It addresses fundamental service-oriented challenges and provides viable solutions that IT professionals can employ:
- A service lifecycle that identifies major modeling disciplines
- Introduction to service-oriented analysis, design, and realization
- Introduction to service-oriented technologies
- A service-oriented integration model that provide viable interoperable solutions
- Service reusability model that elaborates on various methods that can facilitate asset reuse in organizations
I'd recommend this book to IT personnel and SOA practitioners that would like to learn more about starting service-oriented projects and achieving effective results.
Rated by buyers -
This book is a must read for the Executive and Architect responsible for transforming their business processes and IT infrastructure from something resembling an anchor to an agile, flexible system that enables corporate progress. This book will show you a process that will help you get off step 0, define the right services, and ensure that your SOA efforts resolve your business and IT challenges. When implementing an SOA, the technology is the easy part, ensuring that services are created in a consistent manner, that they are designed with reuse in mind, that s/w creation, and hence new product development, gets less expensive and takes less time, over time, that's the hard part, that's where SOA Governance comes in, and this book will give you the SOA Governance basics you need to get your SOA transformation off to a good start. Get control of Governance and your 75% there. This book will not provide code snippets, developer advice, or describe technical specifications, if you want these things, get Thomas Url' or Greg Lomow' books. This book is about using a top-down business service analysis, bottom-up implementation considered, iterative SOA design model. Read it to develop or improve your SOA planning capabilities.
Rated by buyers -
Amazon deleted my last negative review so I'm writing another one. This book is nothing but middle manager buzzwards and little content. Beware all the 5 star 'real name' reviews below. Someone is stacking the deck on this one.
Rated by buyers 
-
Note: My strong dislike of this book probably says more about me than the book...
As a developer I like books that bridge the technical and the business gap. I need to see, in concrete examples, how things might be implemented -- I want to see code, configuration documents, snippets of policy code etc. I also find it helpful when books build upon a sample application. I wanted to see examples of the technology that enables SOA, walk-thrus of standards such WSPL.
This book has none of that. To me it is a book of high-level lists of lists and every section I've read leaves me wondering what it said. I think they repeat themselves too much and the book seems poorly organized with material half way through a chapter which seemed to me to belong at the start. For all it being high-level, they make an assumption that the reader is familiar with a host of acronyms and/or the technology behind them.
Find other books like this one:
