Why should you care?

WhatsApp-style UX needs durable history plus instant delivery. Polling Mongo every second will not scale.

See it live — copy this example

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

db.rooms.insertOne({ _id: "lobby", members: ["u1", "u2"] })
db.messages.insertOne({
  roomId: "lobby",
  senderId: "u1",
  text: "Hello NoSQLVerse",
  at: new Date()
})
db.messages.createIndex({ roomId: 1, at: -1 })
db.messages.find({ roomId: "lobby" }).sort({ at: -1 }).limit(50)
// Live: db.messages.watch([{ $match: { "fullDocument.roomId": "lobby" } }])

Run Example »

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

What happened?

• messages are referenced by roomId with time index for history pages.
• find loads recent messages.
• A change stream filters by room for live fan-out to WebSocket subscribers.

Practice next

1. Create rooms and messages.
2. Page history with limit/cursor on at.
3. Watch inserts for one room in a script.
4. Add reactions array carefully or side collection.
5. Shard by roomId when volume explodes.

Remember

Messages collection + roomId/at index. Change streams power live updates. Paginate history; do not embed forever.

Support chat widget

Shoppers chat with agents; both see new messages via sockets fed by change streams.

Outcome: History loads fast; live typing feels instant.