Where Does Data Live? — Welcome to the Series

Where Does Data Live? — Databases for Non-Developers

---

Why I Wrote This Series

You may have been in a meeting where this happened.

"The engineering team has decided which database we'll use." "Customer data has been leaked — what are we supposed to do?" "We want to adopt AI, but first we need to clean up our data. What does that even mean?"

And in most cases, the non-developers in the room nod and move on. Not because they don't care. Because they don't know what to ask. Topics like databases, governance, and security are written in the language of technical documentation, and that language never assumes a reader who isn't a developer.

Yet when data is wrong, or leaks, or stops working, the fallout doesn't land only on the tech team. It lands on the business owner responsible for revenue, on the service manager who has to send the apology letter to customers, and on the executives who receive the regulatory fine. A decision about a database wears the clothing of a technical decision, but its consequences are entirely business consequences.

So this is why I wrote the series. Not to turn you into a developer, but to turn you into someone who can ask good questions. "What problem does this choice actually solve?" "What exactly does this number mean?" "Have we ever actually restored from a backup?" "Is it okay to hand this data over to AI?" — one question like that preventing a million-dollar mistake happens more often than you'd think.

Who This Is For

• Product managers, planners, and marketers who plan or run digital services
• Small business owners, organization leaders, and founders who handle customer information
• Practitioners and executives who want to ask the important questions in data-related meetings
• Educators, nonprofit staff, and anyone who uses data but doesn't do development

On the other hand, this series will not teach you coding or how to install a database. You won't need to write a single line of SQL. Instead, each part includes "questions you can ask right away in a meeting" and "checklists you can act on today."

What You'll Get from This Series

1. The big picture — why databases exist at all. The perspective that they are the most systematic answer to the problem of "recording, finding, and using" that began when humans first drew pictures on rocks.
2. A working vocabulary — understanding terms like transaction, index, governance, and RAG in everyday language, well enough to hold your own in a conversation with the engineering team or an outside vendor.
3. Criteria for judgment — a list of questions that let you actually evaluate "the most famous product isn't the right answer." Total cost of ownership, RTO/RPO, vendor lock-in, exit strategies, and more.
4. A map of responsibility — who is responsible for what in data governance and security, in incident response, and where your share of the responsibility as a non-developer begins and ends.
5. Sightlines for the era — why "good data" matters more than ever in the AI age. Why Garbage In, Garbage Out is amplified when it meets AI.

What the Series Covers

The series is organized into four acts.

Act 1. Foundations — Why Databases Exist (Parts 1–2) Starting from the history of record-keeping, we ask what a database is and why it exists. Along with the fundamental questions — "why do we store and manage data at all" and "why do we have to do it well" — we build the data → information → knowledge → wisdom ladder, and confirm that the goal of managing and analyzing data is ultimately "wisdom": better action.

Act 2. Types and Choices — Which Container Should You Use? (Parts 3–5) We sort out the forest of database types, from relational to vector databases, and distinguish the roles of operational databases, warehouses, and lakes. Then we set out the criteria for choosing, built around ten questions to ask before you ever ask about a product name.

Act 3. Management and Protection — How Do You Guard What's Inside? (Parts 6–10) The heart of the series. We cover what happens when you put bad goods in a good container (GIGO), governance — giving data an owner and rules, the lifecycle of personal information, the many layers of security, and what to do in what order when a breach happens.

Act 4. A Changing Landscape — Cloud and AI (Parts 11–12) We look at responsibilities that don't disappear even when you hand off operations (the shared responsibility model of the cloud), and what "good data" means in the AI era. We explain what vector search and RAG are, and set out the questions to ask before handing your data over to AI.

The appendix includes a condensed decision checklist for the whole series and a plain-language glossary. Even if you don't read the main text, just opening the appendix before a meeting will help.

How to Read

I recommend reading in order, but each part stands on its own. If a governance discussion is looming, feel free to start with Part 7. If you're evaluating AI adoption, start with Part 12 and work your way back. That said, I do suggest reading the "data → information → knowledge → wisdom" ladder in Part 1 first — the entire series stands on that ladder.

The one sentence that sums up the series A database is not a warehouse where data is piled up. It is a system of promises that keeps an organization's memory accurate and safe.

Now, in Part 1, let's travel back to the moment when humans first carved pictures into rock.

---

Series contents

1. What Is a Database — How Is It Different from an Excel File?
2. How Databases Protect Accuracy — The Principles of Entry, Search, Editing, and Transactions
3. What Kinds of Databases Are There? — From Relational to Vector
4. Databases, Data Warehouses, and Data Lakes — Similar at a Glance, Different in Role
5. Why Choosing the Right Database Matters — The Most Famous Product Isn't the Answer
6. Data Models and Data Quality — Wrongly Stored Data Gives You Wrong Answers, Fast
7. What Is Data Governance? — Data Needs an Owner and Rules for Use
8. Less Personal Information, Only What's Needed — The Lifecycle from Collection to Deletion
9. The Basics of Data Security — One Lock Is Not Enough
10. Why Do Data Breaches Happen, and What Should You Do When One Does?
11. Cloud and Serverless Databases — Handing Off Operations Doesn't Hand Off Responsibility
12. Databases in the AI Age — Vector Search, RAG, and the Era of Good Data

• Appendix. A Database Checklist and Glossary for Non-Developers