Platinum Partner
architects,enterprise-integration,architecture,patterns,dom,tips and tricks,ast,cs

Design Patterns in the Test of Time: Composite

 

The composite pattern describes that a group of objects are to be treated in the same way as a single instance of an object. The intent of a composite is to "compose" objects into tree structures to represent part-whole hierarchies. Implementing the composite pattern lets clients treat individual objects and compositions uniformly.

More on this pattern.

This post is supposed to come on the 1st of Nov or there about, which means that I’m going to do a small divergence into politics now. Here is an example of how the upcoming presidential elections in the states.

        public interface IVotingUnit

        {

            int Weight { get;set; }

            int CandidateId { get;set; }

        }

         

        public class Voter : IVotingUnit

        {

            [Obsolete("Racist")]

           string Id { get;set; }

        

           int Weight { get;set; }

        

           int CandidateId { get;set; }

       }

        

       public class WinnerTakesAllState : IVotingUnit

       {

           string StateCode { get;set; }    

        

           int Weight { get;set; }

           int CandidateId { get;set; }

        

           public void AddVote(Voter vote){

               // calculate

           }

       }

Yes, this is probably a bad example of this, but I find it hilarious.  The basic idea is that you can have an object that represent many other objects, but show the same external interface.

Composites are usually used for the more CS style of programming. Composites are very common in tree structures such as compiler AST or DOM. But beyond that, I can’t easily recall any real world usage of them in my applications. There are usually better alternatives, and you have to remember that when you speak about enterprise applications, loading / storing the data is just as important. And trying to implement the composite pattern under those circumstances will lead to a world of hurt.

Recommendation: If your entire dataset can easily fit in memory, and it make sense, go ahead. Most of the time, you probably should stay away.




Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks
Tweet

{{parent.nComments}}