> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# What is Database
> Explains what a database is and how structure such as fields, records, tables and types turns raw data into searchable, organized, useful information.
Imagine you're planning a trip.
You saved restaurant names in your Notes app, train times in a [WhatsApp message](https://www.whatsapp.com/), hotel details in an email, and there's a screenshot of your [Airbnb booking](https://www.airbnb.com/) somewhere. On the day of the trip you end up scrolling, searching, and probably swearing.
That's the problem with scattered data: the facts exist, but they're not organized, searchable, or connected. Services like [Booking.com](https://www.booking.com/) keep reservations organized, and your phone reminds you about upcoming flights or hotels—mostly thanks to databases.
In this article we'll answer: what is a database, how structure turns raw data into useful information, and where you already see databases at work.
By the end you'll understand why databases are everywhere and why their structure matters.
Practical example: Cody's vet visits
Cody was logging her pet's vet visits in [Google Sheets](https://www.google.com/sheets/about/), but entries were inconsistent:
* 17 July, checkup, Vet Adams, \$35
* 23-07-25, vaccination, 45, Vet Clark
* 30 July, Vet Brown, microchip, USD 100
The facts are present, but without headings, consistent ordering, or uniform formatting the sheet quickly becomes hard to search or summarize. The solution is structure: clearly defined headings (fields), consistent data formatting (types), and one record per visit (row).
Start by assigning clear headings: Date, Reason, Vet, Cost. Each heading is a field. Move each piece of data into the proper column so each row becomes a single record.
Next, enforce the right data type for each field to make sorting and querying reliable:
| Field | Suggested data type |
| ------ | ------------------------ |
| Date | `date` |
| Reason | `text` |
| Vet | `text` |
| Cost | `number` (or `currency`) |
Other common types include `boolean` (true/false) and `integer` vs `float`. Exact names differ between database systems, but the purpose is the same: ensure the right kind of data goes into each field. Relational databases typically enforce this with a predefined schema; some NoSQL systems allow more flexible or dynamic structures.
With headings and types in place, Cody can:
* sort visits by date,
* filter by reason (e.g., vaccination),
* calculate total spending by summing the `Cost` column.
That's the difference between data and information:
* Data: raw numbers, text, and dates.
* Information: structured, searchable, and meaningful data.
Core database concepts
| Term | What it means | Example |
| -------- | ------------------------------------------------------------------- | ---------------------------------------------- |
| Field | A single column that defines one type of data | `Date`, `Name`, `Price` |
| Record | A single row that contains values for all fields | One vet visit entry |
| Table | A collection of related records | `VetVisits` table |
| Database | One or more tables plus rules and indexes that make data manageable | App backend storing contacts, posts, or orders |
Everyday examples
* Contacts app: each person is a record with fields like name, phone, and email.
* Music playlist: song title, artist, and album are searchable fields.
* Social networks and e-commerce: databases track who follows whom, which photos were posted, product details, prices, reviews, and orders.
Think about [Instagram](https://www.instagram.com/): over a billion users, each with posts, followers, and messages. Every like, comment, and follow is managed by databases so the app can display the correct feed and let you search for a friend or hashtag.
Similarly, [Amazon](https://www.amazon.com/) lists millions of products and processes hundreds of millions of orders. Product details, prices, inventory, reviews, and orders are tracked and updated in real time—only possible with robust databases.
Without databases it would be chaos: customers couldn't reliably search, see accurate prices, check availability, or have warehouses ship the right items.
Quick quiz
Which statement is true?
A. A field is a full row of data in a table.\
B. A record stores one specific piece of information.\
C. Structure helps turn data into useful information.
Correct answer: C. Structure lets a database organize raw facts into something we can search, sort, and use.
* Option A is backwards: a field is a single column (e.g., `Date` or `Name`).
* A record is a full row that stores all fields for a single entry (e.g., one vet visit).
Summary
* A database is a structured place to store and organize related information.
* Fields (columns) define the type of data; records (rows) hold complete entries.
* Structure—headings, data types, and consistency—turns raw data into useful information.
* Everyday apps (contacts, music, social media, e-commerce) rely on databases to function at scale.
We'll next explain how databases store structured data using keys, indexes, and relationships.
Databases enforce structure so you can reliably query, sort, and analyze data. Even simple apps depend on this structure to work correctly.