You now have the full core toolkit for working with MongoDB: documents and collections, every CRUD operation, schema design decisions, indexes, the aggregation pipeline, and connecting a real application to it with both the raw driver and Mongoose.
| Topic | Why it matters beyond this course |
|---|---|
| Transactions | Multi-document ACID transactions, for operations that must all succeed or all fail together |
| Replica sets & sharding | How MongoDB scales and stays available in production, not just a single server |
| Change streams | Reacting in real time when data changes, without polling |
| GridFS | Storing files larger than the 16MB single-document limit |
If you have not already, this is a natural point to work through the Building a REST API lesson in the Node.js course — combining what you now know about MongoDB with Express routing is exactly how most real backends are built. If you started this course to pair with the SQL course, revisit SQL Joins side by side with this course's referencing lesson — the same relational thinking, expressed two different ways.
Build something small with all of it
The best way to make any of this stick is a small real project — a to-do list API, a simple blog backend, a notes app — built with Node.js, Express, and MongoDB together, touching insert, find, update, delete, at least one index, and one aggregation query.