|
||||||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||
Frequently Bought Together
Product Details
|
Product Description
Product Description
The patterns are covered in detail making use of several examples providing directions to the readers on how to implement the presented patterns. Additionally, the volume presents a thorough introduction into resource management and a case study where the patterns are applied to the domain of mobile radio networks. The patterns are grouped by different areas of resource management and hence address the complete lifecycle of resources: resource acquisition, coordination and release.
From the Back Cover
As the need for resource management is often discovered late in the software development lifecycle, and changing the system design at this late stage is difficult, it is important that such tasks are performed early in the lifecycle. Since systems belonging to different domains have different system constraints and requirements, a technique that works well in a particular system or configuration might not be so effective in another.
POSA 3 uses patterns to present techniques for implementing effective resource management in a system. The patterns are covered in detail, making use of several examples, and, as in previous POSA volumes, directions are given on how to implement the presented patterns. Additionally, the volume presents a thorough introduction into resource management, and two case studies where the patterns are applied to the domains of ad hoc networking and mobile radio networks. The patterns are grouped by different areas of resource management and hence address the complete lifecycle of resources: resource acquisition, coordination and release.
Resource management in software systems is the process of controlling the availability of resources to resource users. Read the first page
Concordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
4.0 out of 5 stars
Clear and well-written,
By
This review is from: Pattern-Oriented Software Architecture, Patterns for Resource Management (Hardcover)
Of all the design pattern books I've seen, this may be the best-written. Each pattern is covered in the ways you would probably expect: what it is, when it applies, what good and bad effects are likely to follow. This goes a few steps beyond, though. Most patterns are shown in class diagrams, as you'd expect. Interaction diagrams are much more common and complete than in most books, and clearly show the dynamics of different roles working with each other. Multiple different interaction diagrams show multiple different ways to implement the pattern or to put it to use. CRC cards are given for lots of the patterns - among other things, this book gives good examples for people who've never seen CRC cards used before. The exceptional part of this writing is the "implementation" section of each pattern description. It shows the different steps and factors needed for the analysis leading up to pattern use, a welcome change for people new to this level of abstraction. Finally, just about every pattern is illustrated in Java code. This will be very helpful for readers who need a concretion to bring the abstraction to life. I always have mixed feeling about code samples, though. I've seen too many design pattern beginners mistake the example for the rule. They lose out on the breadth of the pattern and the many valid ways to interpret it into a working system. The only drawback to this book is its basic level of presentation. Many of the patterns will be familiar to experienced readers, but that always happens with patterns. The descriptions, however, often miss important topics. This book is dedicated to patterns about resource allocation. They are helpful in resource-constrained embedded systems where deadlock is a real threat; the authors barely mention deadlock, if at all. Resource management, including replication and caching, is also important in parallel and distributed systems. Maintaining global consistency a subtle topic with many variations, and gets just a few paragraphs of discussion. Still the book is a good one over all. The pattern content is good, and the presentation is outstanding.
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
4.3 out of 5 stars (3 customer reviews) 13 of 13 people found the following review helpful
4.0 out of 5 stars
Clear and well-written,
By wiredweird "wiredweird" - Published on Amazon.com
This review is from: Pattern-Oriented Software Architecture, Patterns for Resource Management (Hardcover)
Of all the design pattern books I've seen, this may be the best-written. Each pattern is covered in the ways you would probably expect: what it is, when it applies, what good and bad effects are likely to follow.This goes a few steps beyond, though. Most patterns are shown in class diagrams, as you'd expect. Interaction diagrams are much more common and complete than in most books, and clearly show the dynamics of different roles working with each other. Multiple different interaction diagrams show multiple different ways to implement the pattern or to put it to use. CRC cards are given for lots of the patterns - among other things, this book gives good examples for people who've never seen CRC cards used before. The exceptional part of this writing is the "implementation" section of each pattern description. It shows the different steps and factors needed for the analysis leading up to pattern use, a welcome change for people new to this level of abstraction. Finally, just about every pattern is illustrated in Java code. This will be very helpful for readers who need a concretion to bring the abstraction to life. I always have mixed feeling about code samples, though. I've seen too many design pattern beginners mistake the example for the rule. They lose out on the breadth of the pattern and the many valid ways to interpret it into a working system. The only drawback to this book is its basic level of presentation. Many of the patterns will be familiar to experienced readers, but that always happens with patterns. The descriptions, however, often miss important topics. This book is dedicated to patterns about resource allocation. They are helpful in resource-constrained embedded systems where deadlock is a real threat; the authors barely mention deadlock, if at all. Resource management, including replication and caching, is also important in parallel and distributed systems. Maintaining global consistency a subtle topic with many variations, and gets just a few paragraphs of discussion. Still the book is a good one over all. The pattern content is good, and the presentation is outstanding. //wiedweird 5 of 5 people found the following review helpful
4.0 out of 5 stars
Lookup - very wide scope of usages,
By W Boudville - Published on Amazon.com
This review is from: Pattern-Oriented Software Architecture, Patterns for Resource Management (Hardcover)
Kircher and Jain provide an advanced text on describing patterns, found when you have to code for the management of resources. Where you might have one computer or many scattered across a network that you do not control. (Think Internet.) But text explanations they offer are lucid. And the readership is expected to be highly experienced. So it's very reasonable that you can take high level descriptions of translate these into design documents and ultimately, a functioning system.Of all their patterns, the first one, Lookup, is perhaps the easiest to understand and leads logically into the other more specialised patterns. Also, for Lookup, there is a rather comprehensive list of use cases. Very instructive, in showing that this very first pattern has such wide scope. As in LDAP, CORBA, UDDI, JNDI, Jini and p2p implementations like JXTA. All these have some variant of Lookup as a core and non-trivial central feature. Yet this may be the simplest pattern of the book! A good treatment, to motivate you to continue further and appreciate the other patterns. 4 of 4 people found the following review helpful
5.0 out of 5 stars
Definitive and Comprehensive,
By Ray Ye - Published on Amazon.com
This review is from: Pattern-Oriented Software Architecture, Patterns for Resource Management (Hardcover)
Resource management, the topic is not new. Some people presented a pattern or two in this area, but what makes this book stand out is it is weaving all these patterns together to a pattern language.The book groups the patterns in three categories, resource acquisition, resource lifecycle and resource release. It also provides two case studies. The book only has about 250 pages, yet it provides an extensive coverage of the sphere of resource management. For today's high capability enterprise applications development, resource management is more important than ever before. Resource is not limited to low-level things like CPU power, thread, memory, connections, etc., it also includes components or services accessed by remote client. Enterprise application developer will find this book an indispensable reference for developing efficient, stable, scalable predictable and accessible applications by effective resource management. |
|
Listmania!
Look for similar items by category
- Books > Computers & Internet > Hardware > Design & Architecture
- Books > Computers & Internet > Hardware > Microprocessors & System Design > Computer Design
- Books > Computers & Internet > Programming > Languages & Tools
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Internet > Software
- Books > Qualifying Textbooks - Fall 2007 > Computers & Internet
Look for similar items by subject
Feedback
|
