Why should you care?

Flipkart product pages, chat messages, and IoT sensor readings change shape often. A document store lets you ship a new field (like “dealTag”) without a multi-hour migration on every row.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

// Conceptual: one flexible document vs rigid columns
db.products.insertOne({
  name: "Noise Cancelling Headphones",
  price: 4999,
  tags: ["audio", "wireless"],
  dealTag: "Big Billion Days"   // new field — no schema migration
});

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• insertOne adds one document to the products collection.
• name and price are simple fields.
• tags is an array.
• dealTag appears only on this document — other products can omit it.

Practice next

1. Open mongosh and run: use your database
2. Paste the insertOne example and press Enter.
3. Run: db.products.find().pretty()
4. Add a nested field specs: { batteryHours: 30 } on insert.
5. Insert one product with only { name: "Stub" } and see it still works.

Remember

NoSQL stores flexible documents instead of fixed rows. MongoDB documents are JSON-like (actually BSON under the hood). Add fields when the product needs them — design still matters.

Flipkart catalog fields evolve every festival

Marketing adds “comboOffer” only for festive SKUs. In SQL you often add nullable columns for the whole table. In MongoDB only festive docs carry comboOffer.

Outcome: Catalog ships the offer field the same day without a full-table schema lock.