The Blob

From CloudScale
Revision as of 16:24, 5 November 2013 by CloudScale (Talk | contribs)

Jump to: navigation, search


The Blob

Also Known As

The god class


Assume we have a process controller program. There are Controller and Valve Class as Figure 1 shows. This example is from [1].


Figure 1: Excerpt from a class diagram for a process controller program [1]


Systems with concurrency and mostly those that access a database.


This problem occurs when one class performs most of the system work relegating other classes to minor, supporting roles. As in the example, the Controller does all the system work, openValve and closeValve. The Valve simply reports its status (open or closed) and answers the Controller’s invocation, open and close respectively. The Controller requests information, make decisions and orders the Valve to open or close. For example, if the Controller wants to open the valve, it must get the current status from the valve first and tell the valve to open. See the code below:

void openValve() {

      status currentStatus;
      currentStatus = theValve->getStatus();
      if (currentStatus != open)


In the case when the valve is closed, it costs two messages to open the valve including one unnecessary message. This could potentially lead to unnecessary message traffic, which hinders scalability.


Keep related data and behaviour together. An object should have most of necessary data to make a decision. As in the example of the Controller and the Valve, one possible solution to reduce the messages is to check the valve status locally inside the Valve class (keep related data and behaviour together). So the openValve() operation in Controller is changed to:

 void openValve() {

and the open() operation in Valve becomes:

 void open() {
       if (status != open)
       status = open; 

Now it only requires one message to open the valve.






The anti-pattern potentially causes excessive message traffic.

See also


  1. C. Smith and L. Williams, Software Performance Antipatterns, in Proceedings of WOSP. ACM, 2000, pp. 127–136.