Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects (Hardcover)

~ Douglas Schmidt (Author), Michael Stal (Author), Hans Rohnert (Author), (Author) "This chapter introduces topics related to concurrent and networked objects..." (more)
Key Phrases: queueing layer, asynchronous operation processor, concrete interceptors, Scoped Locking, Thread-Safe Interface, Double-Checked Locking Optimization (more...)

Editorial Reviews

Review

"This book is one of the more important contributions to the literature on 'patterns' and deserves to become a standard text on its specified area of interest."
-- Overload, September 2000

"Let me Start by saying that I highly recommend this book. If you are a reader of the expanding literature on pattern-oriented software design, rush out and buy this book! This book has the potential to be a seminal volume." --Glenn E. Mitchell II, Ph.D.: Microsoft Office Pro; www.msofficepro.com; (5/30/01)

Product Description

Designing application and middleware software to run in concurrent and networked environments is a significant challenge to software developers. The patterns catalogued in this second volume of Pattern-Oriented Software Architecture (POSA) form the basis of a pattern language that addresses issues associated with concurrency and networking. The book presents 17 interrelated patterns ranging from idioms through architectural designs. They cover core elements of building concurrent and network systems: service access and configuration, event handling, synchronization, and concurrency. All patterns present extensive examples and known uses in multiple programming languages, including C++, C, and Java. The book can be used to tackle specific software development problems or read from cover to cover to provide a fundamental understanding of the best practices for constructing concurrent and networked applications and middleware.

See all Editorial Reviews

Product Details

• Hardcover: 666 pages
• Publisher: Wiley; 1 edition (September 14, 2000)
• Language: English
• ISBN-10: 0471606952
• ISBN-13: 978-0471606956
• Product Dimensions: 9.2 x 7.5 x 1.7 inches
• Shipping Weight: 3 pounds (View shipping rates and policies)
• Average Customer Review: 4.3 out of 5 stars  See all reviews (22 customer reviews)
• Amazon.com Sales Rank: #170,721 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #13 in

  Books > Computers & Internet > Hardware > Parallel Processing Computers

Customer Reviews

Most Helpful Customer Reviews

52 of 52 people found the following review helpful:

5.0 out of 5 stars Excellent!, February 7, 2001

By	M. Henning "Michi" (Holland Park, QLD Australia) - See all my reviews (REAL NAME)

The book consists of three sections: a short introduction that outlines the problem space, a section containing a large collection of patterns, and a short final section that talks about weaving patterns into a pattern language and offers a few speculations as to the future of patterns.

The first section is quite short, but covers the problem space nicely and provides the motivation for what follows. The presentation is greatly helped by a case study for applying patterns to a concurrent web server; this illustrates how individual patterns can be used to solve particular problems and provides a practical perspective for how to make use of what is in the remainder of the book.

The second section constitutes the majority of the book and describes a large collection of network and concurrency patterns. Here is where the real meat of the book can be found, with 17 different patterns plus variants. There is something for everyone here, such as interceptor, reactor, acceptor-connector, etc. The patterns are presented clearly, with ample UML diagrams to support the extensive explanations. What I liked particularly is that the presentation is both complete and fair. For example, the double-checked locking pattern isn't just presented as a panacea for singleton initialization. Instead, you get explicit warnings about memory coherency issues, together with examples for how to deal with them, so you don't go and implement something and then wonder why it doesn't work...

The final section of the book shows how to connect patterns into a pattern language, such that each pattern nicely fits into a larger architectural whole. There is also some speculation as to where patterns might be headed next. (According to the authors, we are nowhere near having exhausted the topic.)

Overall, I was really impressed with this book. The text provides extensive references to existing literature, so if you are interested in learning about a particular topic in more detail, you'll find plenty of material for further reading. And there is an index that actually works (which is a rarity these days).

While the language is lucid, the book is probably not something you want to read in a single sitting. Instead, it's the sort of book you browse through, picking up interesting things as you go, and then referring back to them when you need more detail. (I read the book over a number of weeks, digesting a chapter at a time when it suited me.)

Overall, I highly recommend this book. While much of the content has been published previously, it's difficult to find elsewhere and not as up to date. Here, you get everything in one place, presented in a form that works both for learning and as a reference.

If you are interested in programming distributed systems, don't miss this--there is no other book that covers the ground anywhere near as well!

17 of 19 people found the following review helpful:

5.0 out of 5 stars Tools you must have as a programmer and archtitect today, October 29, 2000

By	Bruce R Trask (Riverdale, NY United States) - See all my reviews

I highly recommend this book! If you've ever wrestled with the varying idiosyncrasies of different operating systems' APIs, the gory details of network programming and/or the complexities of multithreaded programming, then you need this book. Even if you haven't yet and are just now getting into network and concurrent programming, then you will need the tools in this book. The writing style is very very easy to read even though it is tackling a complex subject. You can tell as you read it that it was written by programmers who have been in the trenches of network and concurrent programming.

Almost as important as the patterns presented in the core of the book, are the descriptions of the challenges one faces when architecting and writing concurrent and networked software. For me, getting a clear understanding of these exact challenges and difficulties simplified the entire task of distributed programming. Add to that the patterns themselves and I feel anyone who reads this will have a great deal of confidence and competence in concurrent and networked programming.

Each pattern is clearly laid out and includes real-life examples and sample code. Additionally, there are clear descriptions of how these patterns work together to solve real problems. I was able to put the patterns described in this book into immediate use in the large-scale industrial projects that I was and still am working on. And when I say I was able to put them to use, I mean not just sparingly but rather at the very core of the architecture I was building. I can honestly say that the use of the patterns and techniques described in this book has saved me hundreds of hours of time and headache! This book takes what has been, in the past, the skill of only a few programmers and provides you with tools to tackle the complex tasks of architecting and programming concurrent and networked software.

8 of 8 people found the following review helpful:

4.0 out of 5 stars Good Patterns Hidden in Excessive Verbiage, November 21, 2004

By	Louis K. Thomas (St. Louis, MO USA) - See all my reviews (REAL NAME)

First, the patterns in this book are very good. It was nice to see some coverage of low level networking patterns. As an experienced programmer, I was vaguely familiar with many of the patterns already, but it is really helpful to see the lines drawn in the sand, to hear why the authors chose to break things up as they did, and to understand the ramifications of the patterns in greater detail (eg, their clarification of the difference between Observer and Interceptor was quite helpful). I even got to learn some new patterns! (The Leader / Followers pattern was new to me.)

That said, the writing style about drove me BANANAS! I have never lost my place in a sentence when reading a book so many times. I must have read every line twice. Look, I'm a computer geek - I LOVE dense technical books, but this is something else. It's like reading Shakespear, or Charles Dickens. The authors must have been paid by the word. The specific implies the general! Have mercy! I don't need the difference between an interface and its concrete implementation belabored every time it comes up (and in a patterns book, believe me it's often!)