Difference between revisions of "HowNotTos: Anti-Patterns"

From CloudScale
Jump to: navigation, search
 
(4 intermediate revisions by one user not shown)
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 have collected so far.
   
In the following table, we list the anti-patterns we collect.
+
{{HowNotTosList}}
 
{| class="wikitable sortable"
 
! 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]]
 
| A 3-tier architecture that requires multi-tenancy and/or scalability.
 
|}
 

Latest revision as of 10:26, 21 October 2014

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.
The Stifle The Stifle occurs if single datatabse statemens changing the data are executed for the same table in a loop instead in a batch.