Database indexing, explained without the jargon

There is no clever trick in this one, just a handful of decisions worth making deliberately. Here is database indexing without the vocabulary that usually surrounds it.

Performance work is mostly subtraction, which makes it unpopular and effective. Budget a little time for it every quarter and it never becomes a project of its own.

The short version

The right index turns seconds into milliseconds. Small and consistent beats large and occasional here. If two people in the business would answer this differently, that gap is the actual problem.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. There is a version of this that is over-engineered, and it is worth avoiding.

Every index also slows writes, so be deliberate. The cost of getting this wrong is rarely visible on the day it happens. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Where to go from here

Look at the query plan instead of guessing. Small and consistent beats large and occasional here. Write the reasoning down alongside the decision, because the reasoning is what changes first.

In practice

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. Three things worth confirming about database indexing before you move on:

• Someone can say what the current setup is without going to look
• Every index also slows writes, so be deliberate — 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.