The real cost of ignoring multi-tenancy

Teams tend to reach for this after something has already gone wrong. Nobody bills you for neglecting multi-tenancy. The cost shows up somewhere else.

Architecture is the set of decisions that are expensive to reverse, which is the only reason they deserve the name. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Where the cost lands

• Time spent on work that should not have been necessary
• Enquiries that quietly never arrive
• Decide early whether tenants share a database or not
• Rework, once the problem is finally visible

Isolation is a security requirement, not a preference. Getting it slightly wrong is survivable. Ignoring it entirely is not. Write the reasoning down alongside the decision, because the reasoning is what changes first.

Making it stick

Noisy neighbours become a support problem before an engineering one. That sounds obvious written down. It is still the thing most often skipped. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

The short version

The right architecture for a team of three is the wrong one for a team of thirty, and vice versa. Three things worth confirming about multi-tenancy before you move on:

• Someone can say what the current setup is without going to look
• Noisy neighbours become a support problem before an engineering one — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.