The Composite Pattern is one that is not taken advantage of as often as it might outside of frameworks.  This is an approach to design that allows you to treat a family of objects the same.  It is a quintessential reason for and use of an interface.  The flexibility is critical to being able to handle groups of different objects the same way any individual one would be treated. The Composite Pattern Defined As always, we will start with the “Gang of Four” intent to set the stage for our discussion. “Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.” I think it may be most comfortable to focus on... Read more

The Bridge Pattern is commonly configured but often due to templates and generators rather than understanding the true intent.  Since it is more of a design than code implementation, it can be easily missed.  Nevertheless, it is one we often have available and should probably take advantage of more often. The Bridge Pattern Defined As always, we will start with the “Gang of Four” intent to set the stage for our discussion. “Decouple an abstraction from its implementation so that the two can vary independently.” This is simple and easy to see in code.  How often have you seen (for example) an interface and then a class that is the implementation of it?  I have worked on numerous Spring applications that follow this pattern... Read more