An index is a side-structure that lets a database skip work. It costs storage and slows writes; it pays back in reads, often spectacularly. The art is knowing which questions deserve one.
In plain language
In data work, this term tends to appear once an organisation outgrows ad-hoc spreadsheets and starts thinking in pipelines and warehouses. An index is a side-structure that lets a database skip work. It costs storage and slows writes; it pays back in reads, often spectacularly. The art is knowing which questions deserve one. If you are new to the field, the simplest mental model is this: a precomputed shortcut for finding rows quickly. Read it once with that frame in mind, then come back and read it again — that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of Index as the basement of a building: large, quiet, and where almost everything ends up being kept. The room upstairs is what people use; the basement is what makes the room possible.
Where it shows up
Index lives behind dashboards, analytics tools, recommendation engines, and back-office reports. Most users never see it directly. The team that uses it is usually the one looking at numbers all day.
A small example
Imagine the scene above. The role Index plays is the one its blurb describes — A precomputed shortcut for finding rows quickly. When last night's sales numbers arrive in a dashboard this morning, ideas like this are part of the pipework that moved them.
Common misunderstanding
One line to take with you
Index is leverage on what you already have. Shape the data well and the rest gets easier on its own.