Java Reference
In-Depth Information
D ESCRIPTION : Many web designers have no concept of the costs associated
with loading web page items such as graphics or animations. Since items
have incremental load costs, too many objects can doom performance.
M OST FREQUENT SCALE : Enterprise. Most enterprises operate from a
standard template with a common look and feel.
R EFACTORED SOLUTION NAME : Eliminate Extraneous Objects.
R EFACTORED SOLUTION TYPE : Software.
R EFACTORED SOLUTION DESCRIPTION : Often, the number of web page
objects can be reduced through careful user interface design.
T YPICAL CAUSES : This antipattern can occur when graphics are used in
place of text, when image is valued over performance and performance is
not a priority.
A NECDOTAL EVIDENCE : “This site looks cool, but it is dog slow.” “We
have burned up 8 seconds, and we have not even loaded the servlet yet.”
S YMPTOMS , CONSEQUENCES : Poor performance.
A LTERNATIVE SOLUTIONS : Faster connections and better deployment
hardware or architecture.
Excessive Layering
D ESCRIPTION : Object-oriented systems are easy to layer with excessive
complexity that is not required to adequately describe the relationships
and behavior in the model. The complexity of the software can easily out-
pace the capabilities of the hardware platform.
M OST FREQUENT SCALE : Application.
R EFACTORED SOLUTION NAME : Refactor; Integrate Early and Often.
R EFACTORED SOLUTION TYPE : Software.
R EFACTORED SOLUTION DESCRIPTION : Layers can be combined or elimi-
nated based on the requirements of the system.
T YPICAL CAUSES : This antipattern can occur when inexperienced develop-
ers design solutions, or when communication between teams is inade-
quate, such as in geographically distributed groups.
A NECDOTAL EVIDENCE : “I sure hope that this integration works. We
don't have time to recover if it doesn't.” “Do you really need 18 levels of
inheritance in customer ?”
S YMPTOMS , CONSEQUENCES : Poor performance, poor readability.
Search WWH ::




Custom Search