Cloud Computing Design Patterns
by Thomas Erl
Not aging well — the patterns it catalogs are now built into managed services or covered better elsewhere.
- Status
- Read · December 2020
- Bought
- December 19, 2020
- For
- Cloud & platform architects · Engineers building a shared pattern vocabulary · Anyone vetting an early cloud design
Where it earned its place
The one-paragraph verdict
Not aging well. Erl and his co-authors catalog 100-plus cloud patterns, and the visual documentation is genuinely the standout — clean, consistent diagrams of a kind you rarely find collected in one place. The trouble is that each pattern rarely runs past a screen of text, and the problem/solution framing sits at such a high, vendor-neutral altitude that it tells you a pattern exists without telling you how to build it. As a vocabulary-builder it works; as an implementation guide it doesn’t. I keep it as a lookup table, not a tutorial, which is exactly why the rating lands where it does.
Who should read it
Architects and platform engineers who want a common name for “burst offloading” or “redundant storage” before a design review will get value here. So will anyone sanity-checking an early cloud topology. Engineers who already think in distributed-systems terms, or who want copy-pasteable detail, should not bother — the abstraction will frustrate you.
Where it earned its place
It earned its keep during the cloud-to-homelab decision: the catalog gave me a neutral checklist of cloud-native patterns to weigh against, which made it obvious how many I’d be re-implementing by hand on a single-node cluster — and which ones simply didn’t justify the bill.
Skip it if…
You want anything actionable in 2026 — skip it outright. The patterns it named are either absorbed into managed services or better described in more recent books. The field has moved too far since publication to make this worth the time investment.