The organized, queryable store of structured data — and the quiet infrastructure beneath almost everything digital. From paper files and punch-card registers to Edgar Codd's relational model of 1970 and the SQL query language that followed, the database transformed record-keeping into a recombinant power. Any institution that can store, find, and join records can know and act on everyone in them at once. The bank balance, the airline reservation, the state registry, the credit score: all are database queries. So is the targeted advertisement and the watchlist.
In the mid-1970s, a programmer at an American airline could tell you whether a specific flight had seats — but only after consulting a different system from the one that stored passenger names, and a third one that held fare rules. Each system knew one thing. They could not easily talk to each other. Moving data between them meant writing custom code for every combination. Across government agencies, banks, and hospitals, the same problem repeated: each department had its records, locked in formats that resisted connection. The database was the answer to that isolation. Not merely a file cabinet made electronic, but a structured store you could query from any angle — find all passengers on flight 401, or all passengers named Smith who booked within the last week, or all routes that crossed Chicago. The insight behind it was that data should be stored independently of the programs that use it, organized so any question could be asked without rewriting the underlying structure. That insight, articulated by computer scientist Edgar Codd in a 1970 paper on the relational model, became the foundation of the information economy. Almost every institution you deal with today runs on it.