Difference between revisions of "HowNotTos: Anti-Patterns"

From CloudScale
Jump to: navigation, search
(Replaced content with "==HowNotTos: Anti-Patterns== {| class="wikitable sortable" ! Name/Link !! Context |- | One-Lane_Bridge | A 3-tier architecture that requires a scalable middle tier. |-...")
(HowNotTos: Anti-Patterns)
Line 4: Line 4:
 
|-
 
|-
 
| [[One-Lane_Bridge]]
 
| [[One-Lane_Bridge]]
| A 3-tier architecture that requires a scalable middle tier.
+
| 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. It is analogous to the one lane bridge problem in vehicular traffic, where traffic may only travel in one direction at a time, and, if there are multiple lanes of traffic all moving in parallel, they must merge and proceed across the bridge.
 
|-
 
|-
 
| [[SPOSAD CAT]]
 
| [[SPOSAD CAT]]

Revision as of 12:45, 5 November 2013

HowNotTos: Anti-Patterns

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. It is analogous to the one lane bridge problem in vehicular traffic, where traffic may only travel in one direction at a time, and, if there are multiple lanes of traffic all moving in parallel, they must merge and proceed across the bridge.
SPOSAD CAT A 3-tier architecture that requires multi-tenancy and/or scalability.