A table's physical layout should be dictated by how it is read, not by how it happens to be written. Once storage mirrors the shape of the questions the business actually asks, both the database and the people maintaining it get their work cut down for free.
System
Passenger profiling platform
Scale
1B+ rows across 50+ airports
Role
Sole architect and engineer
Stack
PostgreSQL / Partitioning / SQL
In brief At E23 I partitioned the billion-row PostgreSQL table behind the passenger profiling platform by airport and by passenger, so each customer dashboard reads a single airport slice. Queries that used to time out now answer in seconds.
01
The challenge
Analytical questions over more than a billion rows were reading far more data than the customer was entitled to see, and pushing past the request timeout.
02
The approach
Split the table along the two axes that matter — who is asking, and how writes arrive — then rewrite the read path to match.
03
The result
Customer dashboards answer in seconds instead of timing out, upkeep became a bounded operation, and tenancy is enforced by the layout itself.
Fig. 02 — Every customer question is answered inside one lit column
Hover any step to read what it doesTap any step to read what it does