liveBook · Manning

Noisy neighbor problem

As explained in Grokking Software Architecture

Performance or availability degradation caused when one tenant consumes resources shared with other tenants.

Public-cloud customers usually share physical hardware rather than renting a whole machine. Like apartment residents sharing plumbing and hallways, tenants can affect one another: a neighbor using heavy resources may slow your application even when its code is well written. This makes shared hardware an operational constraint to account for when architecting defensively. section 9.1.1 section 9.12

A neighbor goes viral

A startup on the same physical server suddenly consumes network bandwidth or hard-drive speed. Your application may mysteriously slow down, despite having perfectly written code. section 9.1.1

How Grokking Software Architecture covers it

How deep it goes
Defines the shared-resource failure mode through an example, then stops short of detailing mitigation techniques.
Examples
Uses an apartment-sharing analogy and a startup consuming shared network bandwidth or disk speed.
What you can do after
Understand why shared hardware can cause unpredictable application slowdowns despite well-written code.
How it connects
Connects multi-tenancy with cloud architecture and application latency.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.