Link Details

Design patterns are great - they help software architects rely on the collective knowledge and experience gathered from past projects; they also allow designers, developers, and analysts to use a common language. It occurred to me while flipping through the Core J2EE Patterns that several of them are either outdated or at least their utility has been diminished by advances in JavaEE. In this article, I argue that the cost of the additional layer of 'pattern' code should be outweighed by the value the pattern delivers; further, you must evaluate the value when implementing any pattern. I also offer some rules on making these decisions.