(CATEGORY)

Architecture

Here I write about architecture decisions that cost you if you get them wrong. In the article on a database per tenant I describe what I gained on a healthcare platform in America, where every customer had its own database: separate data that is easy to prove, but also changes that must run on every database, backups per customer and a separate place for the overall numbers. In the article on Quote Builder I explain how the price of a quote comes from rules that are data and not from formulas buried in code, how each quote keeps a copy of its form and its price list, and how the hours of support work like an account. Each article says clearly what you gain, what you pay and when the solution is worth it, so you can decide with open eyes. This page lists the 2 articles in the «Architecture» category, written from real work and sorted from the most recent. Each article starts with the answer and continues with the facts behind it.

Articles: Architecture

Illustration: one shared database for all customers next to one separate database for each

ArchitectureJuly 2026 · 11 min read

A database per tenant: what you gain and what you pay

A healthcare platform where every customer had its own database. The isolation you gain is real. You pay for it in migrations, in backups, and in the first analytics query that has to read from a hundred databases.