Field notes
Decisions we have had to defend in a review.
Not thought leadership. These are the architectural arguments we have actually had with clients, written down so you can disagree with us before you hire us.
01Multi-tenant isolation and the cost curvePlatform engineeringRow-level, database-per-tenant, or account-per-tenant is not a security debate. It is a question of which of your costs are fixed, which are marginal, and how much a single mistake is allowed to cost.June 20267 min read02A BFF per client, and when the duplication earns its keepDigital transformationFour gateways for one product looks like waste on a whiteboard. The duplication is real, but it is shallower than it looks — and what it buys is specific enough to test for.March 20266 min read03Stop/Start on burstable Postgres: what it saves, what it breaksCloud engineeringSwitching the database off overnight is the first cost lever everyone reaches for on a burstable tier. It genuinely works — on a smaller share of the bill than people expect, and it quietly takes a set of availability assumptions with it.August 20266 min read