Boring infrastructure is a design decision — The stack a site runs on shows up in the work, usually as the things nobody had time to fix.

Nothing about a queue driver is visible on a page, and yet the choice turns up everywhere: in how quickly an image appears, in whether a deploy is frightening, in how much of a Friday goes to something other than design.

So the rule here is dull on purpose. A relational database, a file cache, blueprints in the repository and content in the database — nothing that needs a diagram to explain.

The interesting part of a site should be the part people can see. Everything behind it earns its keep by being uneventful.