Difference between revisions of "HowNotTos: Anti-Patterns"
From CloudScale
CloudScale (Talk | contribs) (→HowNotTos: Anti-Patterns) |
CloudScale (Talk | contribs) |
||
| Line 1: | Line 1: | ||
==HowNotTos: Anti-Patterns== |
==HowNotTos: Anti-Patterns== |
||
| + | In the following table, we list the anti-patterns we collect. |
||
| + | |||
{| class="wikitable sortable" |
{| class="wikitable sortable" |
||
! Name/Link !! Context |
! Name/Link !! Context |
||
Revision as of 13:51, 5 November 2013
HowNotTos: Anti-Patterns
In the following table, we list the anti-patterns we collect.
| 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. |
| SPOSAD CAT | A 3-tier architecture that requires multi-tenancy and/or scalability. |
