Difference between revisions of "HowNotTos: Anti-Patterns"
From CloudScale
CloudScale (Talk | contribs) |
CloudScale (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | While patterns provide proven solutions with positive effects, anti-patterns record those solutions with negative consequences. Anti-patterns show software engineers what to avoid as well as solutions. |
|
| − | In the following table, we list the anti-patterns we collect. |
+ | In the following table, we list the anti-patterns we have collected so far. |
{| class="wikitable sortable" |
{| class="wikitable sortable" |
||
Revision as of 14:04, 6 November 2013
While patterns provide proven solutions with positive effects, anti-patterns record those solutions with negative consequences. Anti-patterns show software engineers what to avoid as well as solutions. In the following table, we list the anti-patterns we have collected so far.
| Name/Link | Context |
|---|---|
| One-Lane Bridge | A One Lane Bridge occurs, if a passive resource limits the concurrency in an application. Passive resources can be for instance mutexes, connection pools, or database locks. |
| The Blob | The Blob occurs when one class performs most of the system work relegating other classes to minor, supporting roles. |
