Why should you care?

Teams separate environments (NoSQLVerse_dev vs NoSQLVerse_prod) or domains (billing vs analytics) so credentials and backups stay scoped.

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.products.insertOne({ name: "Keyboard", price: 2499 })
show dbs
db.getName()

Run Example »

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

What happened?

• use your database sets the current database.
• The insert actually creates NoSQLVerse if it did not exist.
• show dbs lists databases with size.
• getName() prints the current database name.

Practice next

1. Run use your database and insert one product.
2. Run show dbs and confirm your database appears.
3. Run use otherDb then db.getName().
4. Create NoSQLVerse_test with one insert and dropDatabase() carefully on the test DB only.
5. Run db.stats() inside NoSQLVerse.

Remember

Databases hold collections. Creation is lazy on first write. use switches your shell context.

Tenant isolation by database (small SaaS)

An early multi-tenant app uses one database per large enterprise customer for hard isolation.

Outcome: Backups and deletes for one customer never touch another tenant’s data.