Why should you care?

Clear collection boundaries keep queries fast and code readable. Mixing users and orders in one collection makes every query harder.

See it live — copy this example

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

use NoSQLVerse
db.createCollection("products")
db.products.insertOne({ sku: "KB-01", name: "Mechanical Keyboard", price: 4499 })
show collections
db.products.stats()

Run Example »

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

What happened?

• createCollection makes products explicitly.
• insertOne adds the first document.
• show collections lists names in the current DB.
• stats() shows count and storage info.

Practice next

1. Create the products collection as shown.
2. Insert two more products with different fields.
3. Run show collections.
4. Create readings for IoT samples.
5. Rename practice: copy docs to products_v2 with aggregate $out (advanced).

Remember

Collections store related documents. They are schema-flexible by default. Name them after nouns: users, orders, posts.

NoSQLVerse course content collections

lessons, progress, and quizzes live in separate collections so lesson reads stay light.

Outcome: Progress updates do not lock or bloat the lesson catalog documents.