45a: Architecture Sinkhole Anti-Pattern

When a request is made to a layered architected service, if the request has to go through all the layers without applying any business logic, the situation indicates an architecture sinkhole anti-pattern. This pattern happens often. The healthy ratio is 80%-20%; a maximum of 20% of the requests having sinkhole anti-pattern is considered healthy.

Although it looks like it is happening more in layered architectures, I also saw it often happening in technically distributed architectures such as VIPER architecture in iOS. VIPER is especially criticized for this anti-pattern.


If you're unfamiliar with Zettelkasten: These notes are atomic. The aim is to have one idea in a note. The connections between notes are as important as the notes themselves.

Reply via email

or comment below.