Service-oriented architecture (SOA)
is a way of organizing software. If your company's development projects
That's it, more or less. So why read the book?
We tell the story as simply as possible to keep you from the heartbreak of
My Eyes Glaze Over
). We assume that you have an elementary knowledge of software, but we give you a fast explanation of any phrase that might leave you
The book can make you feel comfortable as you start to work with service-oriented products, but there's more. The level of detail will enable you to get the most out of technical articles and even to explore the
In November 2006, the magazine
published a survey of its readers and found that
is the "technology
In truth, SOA includes ideas that have been around for decades. Information hiding, for example, has long
Our reading, however, is that SOA is both genuine and a
Two characteristics can hasten the transition to SOA. The first is clarity. This book offers technical detail not only because developers need it to fulfill their jobs but because non-developers can interpret situations better if they understand how the technology works.
A second desired characteristic is imagination. Any company can fulfill the promise of the technology to a degree; but the fulfillment is greatest if at least some developers extend their expertise from programming to the details of what the business does and then to the details of what the business might do in the future. To provide insight into the kind of imagination required, this book offers a business scenario.
We'd like to address the reader who is stretching to understand software of any kind.
We hear a whisper from behind us. "Please! You can't expect someone who lacks a background in software to understand the details of SOA!" The objection is duly noted, and now we have a story to tell.
We gave an early copy of this book to a
We want to