About the press
Two clouds, one set of structures.
Isomorphism Press is a technical publisher with a single subject: what it takes to be genuinely good at Amazon Web Services and Google Cloud. We publish long books, slowly, for engineers who are paid to be right about these systems.
Why this press exists
Founded 2021 · Independent · No platform vendor has ever paid for a page of it
There is no shortage of cloud material. There is a shortage of cloud material that survives its own release notes. Most of what gets written about AWS and Google Cloud is organised the way the vendors organise their consoles — one service, one chapter, one walkthrough — and that shape has a short half-life. When the console moves, the book is wrong. Worse, a reader who learned that way has memorised a catalog rather than acquired a model, and the moment they hit a problem the walkthrough did not anticipate, they have nothing to reason from.
Our editorial position is that a cloud platform is best taught as a model. Underneath the several hundred branded services, each provider has made a small number of load-bearing decisions: where the identity boundary sits, what the unit of isolation is, how the network decides where a packet goes, what the control plane guarantees and what it merely attempts, and which operations are one-way doors. Those decisions explain the services. The services do not explain the decisions. A book that teaches the model gives you something you can use on a service that had not shipped when it went to press.
So our books are organised around problems and structures rather than product names. A chapter is called Where State Lives, not “Introduction to DynamoDB.” The services appear — extensively, with real configuration and real failure modes — but they appear as instances of something, and the something is the point.
About the name
- isomorphism
- noun · from Greek isos (equal) + morphe (form)
- A structure-preserving map between two systems: a translation under which the relationships that matter come through intact, so that anything true of one system’s structure is true of the other’s.
The name is a claim, and the claim is this: the two large clouds are not two unrelated bodies of knowledge that a career forces you to learn twice. They are two encodings of a recurring set of structures. Both put a hierarchy above the workload — AWS calls it an organisation and an account, Google calls it an organisation, a folder, and a project — and in both, that hierarchy is simultaneously the identity boundary, the billing boundary, and the blast radius. Both make a routing decision by evaluating a table in a defined order. Both let one principal become another, and in both that is the first thing an attacker reaches for. Both charge you for moving bytes across a boundary, and in both, the topology of those boundaries is the shape of the invoice.
The mapping is not perfect, and pretending otherwise is how people get hurt. A global VPC is genuinely not a regional one; eventual consistency in one control plane is not the same promise as in the other; the defaults differ in ways that matter enormously in an incident. We spend a lot of ink on precisely those places where the correspondence breaks, because a translation is only useful if you know its limits.
But where the structures do correspond — and they correspond far more often than the marketing on either side suggests — knowing one deeply is most of knowing the other. That transferability is the whole return on going deep instead of broad, and it is what this press was founded to sell.
How we publish
Four commitments that hold for every title on the list, with no exceptions and no asterisks.
- DRM-free PDF and EPUB
- Every purchase is a download, not a licence to a reading app. You get a PDF sized for a laptop screen and a reflowable EPUB, both unencrypted, both yours to keep on whatever machine you read on — including the jump box you are debugging from at two in the morning.
- Free updates within an edition
- Cloud platforms move. When a service changes in a way that invalidates a chapter, the author revises it and the revision goes out to everyone who owns that edition, at no cost. We publish the revision date in the front matter so you always know which text you are reading.
- Authors are working practitioners
- We commission from engineers who are on call for the systems they write about: architects, network engineers, data platform leads, SREs. Nobody on our list is writing from the documentation. The war stories in these books are first-hand, and the trade-offs are the ones the author actually had to make.
- Every title is technically reviewed
- Each manuscript goes to at least two reviewers who work on the opposite side of the fence from the author — a GCP specialist reads the AWS book, a security engineer reads the networking book. Every command, template, and console path is executed against a live account before it ships.
The covers
We license no photography and buy no stock illustration. Every jacket on this list is generated geometry, drawn in the browser as vector artwork at the moment you load the page.
Each title is assigned a motif from graph and lattice theory — a lattice, a torus, a spanning tree, a knot — chosen to echo the structure the book is about. The motif is then rendered from an integer seed stored alongside the title, through a small deterministic generator. The same seed always produces the same drawing, down to the last coordinate, which is why a cover looks identical on the shelf page, in your cart, and in the receipt six months later.
Nothing about a jacket is hand-placed. The composition, the line weights, and the palette all fall out of the seed and the title’s hue. It is the same argument the books make, applied to the books themselves: get the structure right and the surface takes care of itself.
latticeA partial order drawn as a grid of covering relations.The Well-Architected Mind torusA closed surface where every path eventually returns.Google Cloud in Depth knotA closed curve that cannot be pulled apart.Identity Is the Perimeter tessellationA plane tiled without gap or overlap.The Warehouse Migration
By the numbers
- Titles in print
- 17
- Contributing authors
- 8
- Curated tracks
- 4
- Pages published
- 5,912
Counted from the live catalog at build time. Page totals are printed page counts, not estimates.
Start with the structure.
Browse the full list by platform, level, and track — or pick up a foundational title and work outward from there.