Service-Oriented Architecture (SOA): Concepts, Technology, and Design [Hardcover]

Thomas Erl (Author)

Book Description

ISBN-10: 0131858580 | ISBN-13: 978-0131858589 | Publication Date: August 12, 2005

This is a comprehensive tutorial that teaches fundamental and advanced SOA design principles, supplemented with detailed case studies and technologies used to implement SOAs in the real world. ***We'll have cover endorsements from Tom Glover, who leads IBM's Web Services Standards initiatives; Dave Keogh, Program Manager for Visual Studio Enterprise Tools at Microsoft, and Sameer Tyagi, Senior Staff Engineer, Sun Microsystems. All major software manufacturers and vendors are promoting support for SOA. As a result, every major development platform now officially supports the creation of service-oriented solutions. Parts I, II, and III cover basic and advanced SOA concepts and theory that prepare you for Parts IV and V, which provide a series of step-by-step "how to" instructions for building an SOA. Part V further contains coverage of WS-* technologies and SOA platform support provided by J2EE and .NET.

Editorial Reviews

From the Back Cover

"Service Oriented Architecture is a hot, but often misunderstood topic in IT today. Thomas articulately describes the concepts, specifications, and standards behind service orientation and Web Services. For enterprises adopting SOA, there is detailed advice for service-oriented analysis, planning, and design. This book is a must read!"

–Alex Lynch, Principal Consultant, Microsoft Enterprise Services

 

"One primary objective of applying SOA in design is to provide business value to the solutions we build. Understanding the right approach to analyzing, designing, and developing service-oriented solutions is critical. Thomas has done a great job of demystifying SOA in practical terms with his book."

–Rick Weaver, IBM Senior Consulting Certified SW I/T Specialist

 

"A pragmatic guide to SOA principles, strategy, and best practices that distills the hype into a general framework for approaching SOA adoption in complex enterprise environments."

–Sameer Tyagi, Senior Staff Engineer, Sun Microsystems

 

"A very timely and much needed contribution to a rapidly emerging field. Through clarifying the principles and nuances of this space, the author provides a comprehensive treatment of critical key aspects of SOA from analysis and planning to standards ranging from WS-specifications to BPEL. I'll be recommending this book to both clients and peers who are planning on embracing SOA principles."

–Ravi Palepu, Senior Field Architect, Rogue Wave Software

 

"Finally, an SOA book based on real implementation experience in production environments. Too many SOA books get lost in the technical details of Web Services standards, or simply repeat vendor hype. This book covers the really hard parts: the complex process of planning, designing and implementing service-oriented architectures that meet organizational goals. It is an essential companion to any software developer, architect, or project manager implementing–or thinking about implementing–a service-oriented architecture."

–Priscilla Walmsley, Managing Director of Datypic

 

"Thomas Erl's Service-Oriented Architecture: Concepts, Technology, and Design is as good an introduction to service-oriented architectures as one could wish for. In a single volume, it covers the entire topic, from theory to real-world use to technical details. The examples are superb and the writing is wonderfully clear."

–Ronald Bourret, Author, "XML and Databases"

 

"Finally an SOA book which gets to the point with real world answers and examples. Erl guides you on a real world SOA journey. From architecture design to industry standards, this book is well written and can be easily referenced for everyday use. When embarking on your own service orientated adventures, this is the book you want in your bag."

–Clark Sell, Vice President, CSell Incorporated

 

"Organizations struggling to evolve existing service-oriented solutions beyond simple Web Services now have an expert resource available. Leading the way to the true service-oriented enterprise, Thomas Erl demystifies the complexities of the open WS-I standards with detailed practical discussions and case studies. Erl's depth and clarity makes this work a superb complement to his Field Guide."

–Kevin P. Davis, PhD., Software Architect

 

"This book is an excellent guide for architects, developers, and managers who are already working with or are considering developing Web Services or Service-Oriented Architecture solutions. The book is divided into four sections. In the first section the fundamental technologies of XML, Web Services and Service-Oriented Architectures are described in detail with attention given to emerging standards. The book is well written and very thorough in its coverage of the subject. I recommend this book highly to anyone interested in enterprise level service architectures."

–Adam Hocek, President and CTO, Broadstrokes, Inc.

 

Additional praise quotes are published at: www.soabooks.com/reviews.asp

 

The foremost "how-to" guide to SOA

Service-Oriented Architecture (SOA) is at the heart of a revolutionary computing platform that is being adopted world-wide and has earned the support of every major software provider. In Service-Oriented Architecture: Concepts, Technology, and Design, Thomas Erl presents the first end-to-end tutorial that provides step-by-step instructions for modeling and designing service-oriented solutions from the ground up.

 

Erl uses more than 125 case study examples and over 300 diagrams to illuminate the most important facets of building SOA platforms: goals, obstacles, concepts, technologies, standards, delivery strategies, and processes for analysis and design.

His book's broad coverage includes

• Detailed step-by-step processes for service-oriented analysis and service-oriented design

• An in-depth exploration of service-orientation as a distinct design paradigm, including a comparison to object-orientation

• A comprehensive study of SOA support in .NET and J2EE development and runtime platforms

• Descriptions of over a dozen key Web services technologies and WS-* specifications, including explanations of how they interrelate and how they are positioned within SOA

• The use of "In Plain English" sections, which describe complex concepts through non-technical analogies

• Guidelines for service-oriented business modeling and the creation of specialized service abstraction layers

• A study contrasting past architectures with SOA and reviewing current industry influences

• Project planning and the comparison of different SOA delivery strategies

The goal of this book is to help you attain a solid understanding of what constitutes contemporary SOA along with step-by-step guidance for realizing its successful implementation.

 

About the Web Sites

 

Erl's Service-Oriented Architecture books are supported by two Web sites. http://www.soabooks.com provides a variety of content resources and http://www.soaspecs.com supplies a descriptive portal to referenced specifications.

 

© Copyright Pearson Education. All rights reserved.

About the Author

Thomas Erl is the world's top-selling SOA author and the Series Editor of the Prentice Hall Service-Oriented Computing Series from Thomas Erl  http://www.soabooks.com/ His first two books, Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services and Service-Oriented Architecture: Concepts, Technology, and Design have become international bestsellers and have been formally endorsed by senior members of major software organizations, such as IBM, Sun, and Microsoft. Thomas is also the founder of SOA Systems Inc. http://www.soasystems.com a company specializing in SOA training and strategic consulting services with a vendor-agnostic focus. Through his work with standards organizations and independent research efforts, Thomas has made significant contributions to the SOA industry, most notably in the areas of service-orientation and SOA methodology. Thomas has had numerous articles and papers published on Web sites and in industry trade magazines, and is a speaker and instructor for private and public events. To learn more, visit http://www.thomaserl.com

 

© Copyright Pearson Education. All rights reserved.

See all Editorial Reviews

Product Details

• Hardcover: 792 pages
• Publisher: Prentice Hall (August 12, 2005)
• Language: English
• ISBN-10: 0131858580
• ISBN-13: 978-0131858589
• Product Dimensions: 9.4 x 7.4 x 1.9 inches
• Shipping Weight: 3.7 pounds (View shipping rates and policies)
• Average Customer Review: 4.0 out of 5 stars  See all reviews (63 customer reviews)
• Amazon Best Sellers Rank: #233,806 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

43 of 45 people found the following review helpful:

5.0 out of 5 stars Chapter by Chapter Review, May 25, 2006

By 

M. Carter (reviewer) (Albuquerque, New Mexico) - See all my reviews

This review is from: Service-Oriented Architecture (SOA): Concepts, Technology, and Design (Hardcover)

This book is superb. I have read every SOA book available (up until Apr/06) because it's part of my job as a technology research analyst and all-around techno-geek. From those that I have read and studied, this is the only one I feel compelled to write a review about. AND - because I did have to go through it in such detail I'm going to raid my research notes and share with you a detailed review of not just the book, but each of its chapters.

Chapter 1 - Introduction
Nothing special here, this is just a chapter that introduces the rest of the book. Call it a glorified table of contents if you will. At first I felt like skipping it altogether, but then I did what I'm supposed to do for my job and that is read each and every part. In the end, I'm glad I took the time for two reasons: By reading a summary of each of the chapters I got a good feel for what this book was going to cover and what it wasn't going to cover. Secondly, I liked the author's intro stuff about ideal and not so ideal (real) SOA. Kind of insightful and stinging at the same time. Still, though, this is still just a description of other chapters. It's also a chapter you can get for free at the book's web site.

Chapter 2 - Case Studies
Here the author provides background information for the two companies he uses as case studies. If you're into case studies, then you'll definitely want to read through this. But - I found the subsequent samples pretty easy to follow and I think you could get away with skipping this chapter if you really wanted to.

Chapter 3 - Introducing SOA
Here's where I started getting into the meat of the book. If you think you don't understand what soa is or what the industry's made of it or turned it into then you need to read this chapter. It breaks it all down and builds it all up again in a very systematic manner. Make sure you leave this chapter with an understanding of how primitive and contemporary variations of soa are different because the author uses these terms later.

Chapter4 - The Evolution of SOA
Finally someone who makes a distinction between specification and standard and gets it right. This chapter talks about the soa industry and how vendors are responsible for soa but are also causing problems at the same time. How standards organizations are working for soa but also competing at the same time. Pretty interesting stuff and even though this was the least technical chapter, not once was I bored. It ends by comparing Ssoa with older architectures. I especially like how the author differentiates between soa and "traditional" distributed architecture that uses web services. (hint: rpc has a lot to do with it)

Chapter 5 - Web services and primitive soa
I read the author's first soa book last year and this chapter seemed to repeat a few sections from that. But if I remember correctly it goes into more detail and provides case study examples that the first book didn't have. If you're a web services veteran you can probably skip this one.

Chapter 6 -Web Services and Contemporary SOA (Part I: Activity Management and Composition)
Here he goes up a gear and dives right into that scary thing we've been calling ws-* Everything from transactions to context mgmt to orchestration and so on is covered. I really felt the author did a brilliant job building this chapter up by starting with simple meps and building up to activity management and bpel and so on. He really showed how each adds a layer over the other and how all add layers to soa.

Chapter 7 - Web Services and Contemporary SOA (Part II: Advanced Messaging, Metadata, and Security)
Yup, the rollercoast ride continues here as he gets into addressing, reliable messaging, security and other ws-* specs. All of these are specs I had already heard about and I think this type of coverage is appropriate forwhere soa is going. I forgot to mention that in this chapter and 6 he introduces 'in plain english' sections that are hilarious. They are humorous analogies that compare these complex technologies to analogies he writes about a car wash. Good, fresh writing in the usual dull and dry techno world.

Chapter 8 - Principles of Service-Orientation
Essentially a whole bunch of theory about designing services and then eight specific 'principles' (dos and don'ts) about how to design services the right way for soa. I had to go back and reread this chapter after I finished the book. I sort of glanced thru it at first but then found out that later chapters really use these principles. When I went through it again I actually thought this was pretty important stuff. This really is the next oo. You can get this chapter for free at the book web site too.

Chapter 9 - Service Layers
STudy this if you're a application architect or enterprise architect. It shows what you canh do with services built with service-orientation. The diagrams showing different types of layers combined together are pretty cool.

Chapter 10 - SOA Delivery Strategies
If you're a PM you'll love this chapter. It gets into the different phases in a soa project and how you can reorganize them using 'delivery strategies' depending on your budgets and priorities. I'd pay extra close attention to the pros and cons parts where, after documenting these strategies in abstract, the author points out their true colors.

Chapter 11 + 12 - Service-Oriented Analysis I + II
Don't know where to start when it comes to figuring out your services? Well, the author lays it all out here. He provides a process for systemtically breaking down your business logic and divying it up into services. Chapter 12 is like an instruction manual about service model. Being froma web services background this was all new to me.

Chapter 13 - 16 - Service-Oriented Design I, II, III, IV
Roll up your sleeves man, because here is where you get into the real muck of building web services for an soa. There are a bunch of processes that hash out the nitty gritty of wsdl, xsd, and bpel and show you how to build services for the types of layers set up in ch.9. Tons of code and case study samples and tips for design. This is probably the most valuable part of the book for developers and architects.

Chapter 17- Fundamental WS-* Extensions
I forgot tomention that in chapters 6 and 7 no code samples are given. He only covered ws-* specs conceptually. All of the corresponding code is placed in this chapter. A bit inconvenient if you're a developer who wants to see the code while learning about the spec, but not tragic. The neat thing is he ties the code samples into the case studies. This was my first experience with ws-* in real world tyhpe scenarios.

Chapte r18 - SOA Platforms
The author documents j2ee and .net frameworks here first in total abstract and then about how they support the different parts of soa. This was very interesting because it related a lot of the concepts stuff to actual technology and the let you compare different technologies in how they support soa.

I recommend this book to colleagures and clients and I'm recommending it here. If you have questions about SOA then this book probably has the answers you're looking for. I say that because by the time I finished reading it I ran out of questions myself.

35 of 40 people found the following review helpful:

2.0 out of 5 stars Verbose, Mostly High Level Concepts, August 26, 2006

By 

David Douglass (Bloomingdale, NJ) - See all my reviews
(REAL NAME)   

Amazon Verified Purchase

This review is from: Service-Oriented Architecture (SOA): Concepts, Technology, and Design (Hardcover)

This book might be best described as SOA for managers. Most of the book covers high level concepts. In some parts everything is presented as an abstraction, leaving the reader to wonder what the connection with the real world is.

Even as a book focused on a high level overview this book doesn't work. This should have been a 300 page book. Who has time to put up with an extra 400 pages?

If your interest is in actually implementing something, you'll need to go far beyond this book. I've given it 2 stars instead of 1 because I did learn a few things from it.

9 of 9 people found the following review helpful:

2.0 out of 5 stars Excessively long winded for my use, December 14, 2007

By 

Steven R. Mocarski (New York, NY) - See all my reviews
(REAL NAME)   

This review is from: Service-Oriented Architecture (SOA): Concepts, Technology, and Design (Hardcover)

It's hard to understand how the same author wrote this and SOA Principles of Service Design (The Prentice Hall Service-Oriented Computing Series from Thomas Erl) and Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services (The Prentice Hall Service-Oriented Computing Series from Thomas Erl), both of which had more useful information in a much more compact package.

The only real use I can think of for this book is perhaps to quote in a sales context regarding the benefits of SOA to someone who hasn't heard of it. That said, although I believe in SOA as a powerful mechanism, I believe the claims in the book are less well supported then the heft of the book might imply. Other technical details like the importance of UDDI are largely out of date.

I disagree with some of the other reviewers who call the book overly theoretical: I would not give it that much credit. Theory would call on or reference solid research; this book provides anecdotal evidence at best.

Aside from some potential use to sales folks (perhaps why Sun, IBM and MS endorse the book), I think most will want to pass on this one.