MongoDB Administration

🍃 MongoDB Administration

From complete scratch to production-ready — explained simply

💡 Think of this page like your own personal MongoDB notebook. Every section builds on the last — start from the top if you’re new, or jump straight to the cheat sheet if you just need a quick reminder.

1. What even is MongoDB? 🤔

Imagine a filing cabinet 🗄️. In old-school databases (like MySQL), every drawer (table) must hold identical index cards — same fields, same order, no exceptions.

MongoDB is more like a box of sticky notes 📝. Every note can have different information on it — some short, some long, some with extra details — and you just toss them all into the same box (called a collection).

🧠 Simple example: A “Students” collection could have one document for a student with just a name and age, and another document for a student that also includes their favorite subjects. No problem — MongoDB doesn’t force every document to look the same.

Quick Vocabulary

Word you already know (SQL)	MongoDB word	Simple meaning
Table	Collection	A folder of related sticky notes
Row	Document	One sticky note
Column	Field	One piece of info on the note
Primary Key	_id	The unique sticker on every note

A Real Document (in plain JSON)

{
  "_id": "abc123",
  "name": "Bhaskar",
  "hobbies": ["cricket", "coding"],
  "isLearning": true
}

That’s it — that’s a whole “row” in MongoDB. Simple, readable, no complicated table setup needed.

---

2. Getting It Running on Your Computer 💻

1. Download MongoDB Community Server → mongodb.com/try/download/community
2. Also grab MongoDB Compass — it’s a friendly visual app so you don’t have to type every command
3. Open your terminal and type:

mongosh

If you see a prompt like test>, congratulations — MongoDB is running and talking to you! 🎉

---

3. Your First Real Actions (CRUD) 🛠️

Think of CRUD like managing a to-do list app:

✅ Create — add a new to-do

🔍 Read — check your to-do list

✏️ Update — mark a task as done

🗑️ Delete — remove a finished task

Example: A Simple To-Do App in MongoDB

Add a task (Create)

db.todos.insertOne({ task: "Finish BrainBackup site", done: false })

See all tasks (Read)

db.todos.find()

Mark it done (Update)

db.todos.updateOne(
  { task: "Finish BrainBackup site" },
  { $set: { done: true } }
)

Remove it (Delete)

db.todos.deleteOne({ task: "Finish BrainBackup site" })

That’s genuinely 90% of what you’ll do day-to-day as a beginner. Everything else builds on these four moves.

---

4. Indexes — Your Database’s Table of Contents 📖

Imagine searching for one specific recipe in a 1,000-page cookbook with no table of contents — you’d have to flip through every page. That’s what MongoDB does without an index (called a “collection scan”).

An index is like adding a table of contents — MongoDB jumps straight to the right page.

// "Add a table of contents sorted by name"
db.users.createIndex({ name: 1 })

⚠️ Don’t over-do it: Adding too many indexes is like printing 20 different tables of contents for the same book — it takes up space and slows down adding new pages (writes). Only index what you actually search by often.

---

5. Aggregation — Asking Smart Questions 📊

Aggregation is how you ask MongoDB questions like “Who are my top 5 customers this month?” instead of just “show me everything.”

Think of it like a factory assembly line — data goes in one end, passes through stations that filter, group, and sort it, and comes out the other end as a clean answer.

db.orders.aggregate([
  { $match: { status: "completed" } },   // Station 1: only completed orders
  { $group: {                             // Station 2: group by customer
      _id: "$customerId",
      totalSpent: { $sum: "$amount" }
  }},
  { $sort: { totalSpent: -1 } },          // Station 3: highest spenders first
  { $limit: 5 }                           // Station 4: just the top 5
])

---

6. Replication — Never Put All Your Eggs in One Basket 🥚🧺

A Replica Set = keeping identical copies of your data on multiple servers, so if one crashes, another instantly takes over.

        🟢 PRIMARY (handles all writes)
              │
     ┌────────┴────────┐
   🔵 COPY 1          🔵 COPY 2
  (ready to take over if needed)

✅ Real talk: This is the difference between “our app went down for 3 hours” and “our app didn’t even blink” when a server fails.

---

7. Sharding — When One Filing Cabinet Isn’t Enough 🗄️🗄️🗄️

When your data grows too big for one server, sharding splits it across many servers — like moving from one filing cabinet to a whole filing room, with a smart receptionist (mongos) directing every request to the right cabinet.

sh.shardCollection("mydb.orders", { customerId: 1 })

---

8. Backups — Your Safety Net 🪂

# Take a backup
mongodump --db=mydb --out=/backup/2026-07-31

# Restore it
mongorestore --db=mydb /backup/2026-07-31/mydb

🧠 Golden rule: A backup you’ve never tested restoring is basically a backup that doesn’t exist. Test it occasionally!

---

9. Security — Locking the Front Door 🔐

use mydatabase
db.createUser({
  user: "appUser",
  pwd: "StrongPassword123",
  roles: [ { role: "readWrite", db: "mydatabase" } ]
})

Give each app user only the access it actually needs — like giving a house guest a key to the guest room, not the whole house.

---

10. Keeping an Eye on Things 👀

db.serverStatus()   // "How is my server feeling today?"
db.currentOp()      // "What is it doing right now?"

---

📋 Quick Cheat Sheet

Connect

mongosh "mongodb://user:pass@host:27017/dbname"

Basics

show dbs
use mydb
show collections

CRUD

db.col.insertOne({...})
db.col.find({...})
db.col.updateOne({filter}, {$set:{...}})
db.col.deleteOne({...})

Indexes

db.col.createIndex({ field: 1 })
db.col.getIndexes()

Backup

mongodump --db=mydb --out=/backup
mongorestore --db=mydb /backup/mydb

---

✍️ Keep adding your own real-world notes here as you learn — this page grows with you.