For architectural patterns, the authors look at the Layers pattern, used in operating systems such as Windows NT and virtual machines. They also consider Pipes and Filters, which process streams of data. (This pattern, the authors point out, is a lynchpin of Unix.) Their Blackboard pattern shows how a complex problem, such as image or speech recognition can be broken up into smaller, specialized subsystems that work together to solve a problem. (For recognizing words from a raw waveform input, a Blackboard approach might have separate processes to find phonemes, then words, then sentences.)
This book also looks at today's distributed systems in considering the Broker pattern, which is used on the Internet and in Microsoft's OLE technology. This section also presents several powerful patterns for building effective graphical user interfaces, such as Model-View-Controller.
The authors define several well-known design patterns, such as the Proxy and Command patterns, and also basic, far-reaching patterns, such as Whole-Part and Master-Slave, which are widely used throughout computing. Their survey ends with a discussion on the way objects can communicate (using such patterns as Forwarder-Receiver, Client-Dispatcher-Server, and Publisher-Subscriber), which many developers will recognize as familiar patterns, but are codified here as "official" patterns. The book then discusses some idioms in C++ and a more far-reaching role for patterns in software design and architecture. By fitting patterns into traditional software engineering practices, the authors of Pattern-Oriented Software Architecture successfully argue that the role for patterns will only continue to diversify and enrich tomorrow's software engineering tools and methodologies. --Richard Dragan
This book deals with real world situations where programming projects are large and complex and done in teams.
In reality, as anyone who has read Vlissides' other book which spends its whole duration talking just about Visitor, the opposite is true.
The GoF book provides more practical and easy to implement design level patterns, so I suggest you start from it first.
This is a good mix between Fowlers Patterns of Enterprise Applications and the Gang of Four book. It has more high level and complex patterns than the GOF book, but it is more... Read morePublished 18 months ago by Arthur J Correa
This book uses an easy way to explain system patterns. I think every software developer has to read this book; it's a nice reference to help software architects doing a well-done... Read morePublished on September 5, 2006 by Alexandre A. Santos
Second best isn't bad when the #1 book changed forever the way software architecture is talked about. Read morePublished on October 22, 2005 by Amazon Customer
This is an unusual book in the pattern genre. It presents a number of patterns, categorized by archtiectural level. That's just the first part of the book, though. Read morePublished on June 25, 2004 by wiredweird
This book is ten times better than GoF or Fowler's book. I would love to see another volume in this series covering Web Services and Integration patterns, maybe written by Ambler,... Read morePublished on September 24, 2003 by Markandeya Udhayasooriyan
POSA1 is written far better than other related texts, such as GoF. (And be aware of the fact that GoF only contains design level patterns - it does not contain system architecture... Read morePublished on June 15, 2003 by Erik Gfesser
I recommend this book for students like me who are taking intermediate computer science courses for the the following reasons. Read morePublished on June 1, 2003 by "binata"
There is a basic problem with the pattern literature. It is usually as easy to read as a cookbook. This book can actually and worthwhile be read from cover to cover. Read morePublished on February 19, 2002 by ws__
If you're writing a book on patterns, then I think the ones you should pick are ones that _aren't_ straightforward. Read morePublished on October 24, 2001 by Brandon Corfman