MongoDB is a widely used NoSQL database designed to store, manage, and retrieve high volumes of unstructured data. One of the core aspects of working with any database system is the ability to perform fundamental data operations. In MongoDB, these operations are summarized using the acronym CRUD, which stands for Create, Read, Update, and Delete. Each of these operations is essential for manipulating and managing data stored in a MongoDB collection. Understanding CRUD operations is critical for developers, database administrators, and data analysts who interact with MongoDB in real-world applications. This section provides an in-depth overview of each CRUD operation, starting with an introduction to MongoDB and progressing to how these operations function.<\/p>\n\n\n\n
MongoDB is a document-oriented NoSQL database that uses JSON-like documents with optional schemas. It is designed for scalability, high availability, and performance. Unlike relational databases that store data in rows and columns, MongoDB stores data in flexible, JSON-like documents. This flexibility allows developers to quickly evolve applications without the need for extensive database redesign. MongoDB supports embedded documents and arrays, which allows for more complex data structures to be represented easily. This approach to data storage provides a more natural representation of hierarchical relationships, making it ideal for various use cases such as content management systems, real-time analytics, and Internet of Things applications.<\/p>\n\n\n\n
CRUD operations represent the basic set of operations that any data-driven application must support. These operations are used to manage the lifecycle of data stored in a database. In MongoDB, CRUD operations provide a straightforward way to interact with the database. Whether you’re adding new records, querying for specific documents, updating existing records, or removing obsolete entries, CRUD operations are the tools that make this possible. They form the building blocks of any interaction with MongoDB. Mastery of these operations allows developers to write efficient and effective data manipulation code, automate tasks, and ensure data integrity across applications. Understanding these operations in detail is essential for building scalable and maintainable applications that use MongoDB as their backend.<\/p>\n\n\n\n
The Create operation in MongoDB is used to insert new documents into a collection. When a new piece of data needs to be stored, the Create operation is executed. MongoDB does not require predefined schemas, allowing documents within a collection to have different fields or structures. This makes the Create operation very flexible, as developers are not limited by rigid table definitions as in traditional relational databases. A document in MongoDB is a set of key-value pairs, and inserting a document involves specifying these pairs according to the structure required by the application. When the Create operation is executed, MongoDB stores the document in the specified collection. If the collection does not exist, MongoDB will automatically create it before inserting the document.<\/p>\n\n\n\n
The primary command used to insert a document into a MongoDB collection is the insert() method. The basic syntax for inserting a single document is as follows
db.collection.insert({key1: value1, key2: value2})
This command will insert a new document with the specified key-value pairs into the specified collection. For example
db.students.insert({name: “John”, age: 22, course: “Computer Science”})
This command adds a new student record to the “students” collection. If the “students” collection does not exist, MongoDB will create it automatically and then insert the document.<\/p>\n\n\n\n
In addition to the basic insert() method, MongoDB also provides insertOne() and insertMany() methods for more specific use cases.
insertOne() is used to insert a single document, similar to insert()
insertMany() allows for inserting multiple documents at once, improving efficiency and reducing the number of round trips to the database.
Example
db.students.insertMany([{name: “Alice”, age: 21}, {name: “Bob”, age: 23}])
This command inserts two student records into the “students” collection in a single operation.<\/p>\n\n\n\n
MongoDB uses a special field called _id as the primary key for each document. This field must contain a unique value for each document in a collection. If an insert operation attempts to insert a document with a duplicate _id value, MongoDB will throw an error. If _id is not specified, MongoDB automatically generates a unique ObjectId. This behavior helps prevent accidental overwrites and ensures that each document can be uniquely identified.<\/p>\n\n\n\n
MongoDB allows developers to configure the level of acknowledgment required from the database when performing write operations. This is controlled using write concern settings. By default, MongoDB waits for a basic acknowledgment from the primary replica set member before confirming a successful insert. Developers can configure higher levels of write concern for more durability, such as waiting for acknowledgment from multiple replica set members. This is particularly important in distributed systems where consistency and reliability are critical.<\/p>\n\n\n\n
The Read operation retrieves documents from a collection. In MongoDB, this is done using queries that match specific criteria. Queries are expressed using JSON-like syntax, which allows for powerful filtering and projection capabilities. Unlike traditional SQL SELECT statements, MongoDB queries can work with nested fields and arrays, enabling developers to retrieve complex data structures efficiently. The Read operation is essential for any application that needs to display or process stored data. Whether you’re showing a list of users, retrieving product details, or generating reports, the Read operation allows you to access the data you need.<\/p>\n\n\n\n
The primary method used for reading documents in MongoDB is the find() method.
db.collection.find(query, projection)
The query parameter specifies the criteria used to filter documents, while the projection parameter specifies which fields should be returned. For example
db.students.find({age: 22})
This query retrieves all documents from the “students” collection where the age is 22.
To retrieve only specific fields
db.students.find({age: 22}, {name: 1, _id: 0})
This query returns only the “name” field and excludes the _id field.<\/p>\n\n\n\n
Sometimes, you only need a single document rather than a list of matching documents. MongoDB provides the findOne() method for this purpose.
db.collection.findOne(query)
For example
db.students.findOne({name: “Alice”})
This command returns the first document in the “students” collection where the name is “Alice”. It is useful when the query is expected to return a single result, such as retrieving user credentials or configuration settings.<\/p>\n\n\n\n
MongoDB supports a wide range of query operators that enhance the flexibility and power of the Read operation. These include comparison operators like $gt (greater than), $lt (less than), and $eq (equal), as well as logical operators like $and, $or, and $not.
Example
db.students.find({age: {$gt: 20, $lt: 25}})
This query retrieves students whose age is greater than 20 and less than 25.
The use of these operators allows for constructing complex queries that can handle a wide range of application needs.<\/p>\n\n\n\n
When using find(), MongoDB returns a cursor object that allows for efficient iteration over the result set. This cursor can be looped through using various programming languages or MongoDB shell commands.
Example using a loop
var cursor = db.students.find({})
while(cursor.hasNext()) { printjson(cursor.next()) }
Cursors allow developers to handle large result sets without consuming excessive memory, as documents are retrieved in batches rather than all at once.<\/p>\n\n\n\n
Projection is a feature that allows you to control which fields are included in the results of a query. This can reduce network overhead and improve performance by returning only the data that is needed.
Example
db.students.find({}, {name: 1, age: 1, _id: 0})
This query retrieves only the name and age fields for all students and excludes the default _id field. Projection is especially useful in applications that display data in summary views or dashboards.<\/p>\n\n\n\n
Understanding the Create and Read operations in MongoDB is the foundation for effectively managing data within a database. These operations allow developers to store new data and retrieve existing data based on flexible, schema-less structures. MongoDB\u2019s ability to handle dynamic documents and complex queries provides developers with a powerful tool for building scalable applications. With the basics of Create and Read operations covered, the next step is to explore the Update and Delete operations, which will be addressed in the following section.<\/p>\n\n\n\n
The Update operation in MongoDB allows you to modify existing documents within a collection. This operation is essential for maintaining data integrity and ensuring that stored information reflects the most current state. MongoDB supports a wide range of update options, including modifying specific fields, replacing entire documents, and applying conditional updates. Updates can be performed on a single document or multiple documents that match a given query. The flexibility of MongoDB\u2019s update operators enables developers to perform complex modifications with minimal effort. By learning how to use these update methods and operators effectively, you can ensure that your data stays accurate and up to date across various application use cases.<\/p>\n\n\n\n
MongoDB provides several methods for performing update operations. The most commonly used are updateOne(), updateMany(), and replaceOne(). The basic syntax is as follows:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.collection.updateOne(<\/p>\n\n\n\n
<filter>,<\/p>\n\n\n\n
<update>,<\/p>\n\n\n\n
{ upsert: <boolean> }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
The updateOne() method updates the first document that matches the filter criteria.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.updateOne(<\/p>\n\n\n\n
{ name: “Alice” },<\/p>\n\n\n\n
{ $set: { age: 24 } }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This updates the age of the first student named “Alice” to 24.<\/p>\n\n\n\n
The updateMany() method updates all documents that match the filter criteria.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.updateMany(<\/p>\n\n\n\n
{ course: “Mathematics” },<\/p>\n\n\n\n
{ $set: { status: “active” } }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This sets the status to “active” for all students enrolled in the Mathematics course.<\/p>\n\n\n\n
The replaceOne() method replaces an entire document, except for the _id field.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.replaceOne(<\/p>\n\n\n\n
{ name: “John” },<\/p>\n\n\n\n
{ name: “John”, age: 25, course: “Physics” }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This completely replaces John\u2019s existing document with a new one.<\/p>\n\n\n\n
MongoDB provides several update operators to allow partial modification of documents:<\/p>\n\n\n\n
Example using multiple operators:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.updateOne(<\/p>\n\n\n\n
{ name: “Bob” },<\/p>\n\n\n\n
{<\/p>\n\n\n\n
$set: { age: 23 },<\/p>\n\n\n\n
$inc: { credits: 3 },<\/p>\n\n\n\n
$unset: { temporary: “” }<\/p>\n\n\n\n
}<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This updates Bob\u2019s age, increases his credits by 3, and removes the temporary field.<\/p>\n\n\n\n
The upsert option tells MongoDB to insert a new document if no document matches the filter.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.updateOne(<\/p>\n\n\n\n
{ name: “Emily” },<\/p>\n\n\n\n
{ $set: { age: 22, course: “Biology” } },<\/p>\n\n\n\n
{ upsert: true }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
If no student named Emily exists, MongoDB will create a new document with the provided fields.<\/p>\n\n\n\n
MongoDB allows updates to array fields using operators like $push, $pull, and $addToSet.<\/p>\n\n\n\n
Example \u2013 Pushing to an array:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.updateOne(<\/p>\n\n\n\n
{ name: “David” },<\/p>\n\n\n\n
{ $push: { grades: 85 } }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This adds the value 85 to David\u2019s grades array.<\/p>\n\n\n\n
Example \u2013 Pulling from an array:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.updateOne(<\/p>\n\n\n\n
{ name: “David” },<\/p>\n\n\n\n
{ $pull: { grades: 60 } }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This removes the value 60 from David\u2019s grades array.<\/p>\n\n\n\n
Advanced updates can use array filters to update specific elements in arrays.<\/p>\n\n\n\n
Example \u2013 Updating a specific element in an array:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.classes.updateOne(<\/p>\n\n\n\n
{ _id: 1, “students.name”: “Anna” },<\/p>\n\n\n\n
{ $set: { “students.$.grade”: “A” } }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This updates the grade of the student named Anna in the students array of the document with _id 1.<\/p>\n\n\n\n
Array filters can also be used when updating nested arrays:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.classes.updateOne(<\/p>\n\n\n\n
{ _id: 1 },<\/p>\n\n\n\n
{ $set: { “students.$[elem].grade”: “B+” } },<\/p>\n\n\n\n
{ arrayFilters: [ { “elem.grade”: “C” } ] }<\/p>\n\n\n\n
)<\/p>\n\n\n\n
This sets the grade to “B+” for all students who currently have a grade of “C”.<\/p>\n\n\n\n
By default, update operations return a result object with metadata:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
{<\/p>\n\n\n\n
acknowledged: true,<\/p>\n\n\n\n
matchedCount: 1,<\/p>\n\n\n\n
modifiedCount: 1<\/p>\n\n\n\n
}<\/p>\n\n\n\n
This provides useful information about whether a match was found and whether any modifications were made.<\/p>\n\n\n\n
The Delete operation in MongoDB is used to remove documents from a collection. Like the Update operation, deletion can target a single document or multiple documents that match a specific condition. Deletion is an irreversible operation, so it’s important to use it carefully. MongoDB provides built-in safety measures such as write concern and filtering to ensure deletions occur only where intended. Effective use of the Delete operation is crucial for maintaining data cleanliness, freeing storage, and removing outdated or incorrect records from your collections.<\/p>\n\n\n\n
MongoDB provides two primary methods for deletion:<\/p>\n\n\n\n
Basic syntax:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.collection.deleteOne(<filter>)<\/p>\n\n\n\n
db.collection.deleteMany(<filter>)<\/p>\n\n\n\n
The deleteOne() method removes the first document that matches the query.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.deleteOne({ name: “Alice” })<\/p>\n\n\n\n
This deletes the first document where the name is “Alice”.<\/p>\n\n\n\n
The deleteMany() method removes all documents that match the query.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.deleteMany({ status: “inactive” })<\/p>\n\n\n\n
This deletes all students with the status set to “inactive”.<\/p>\n\n\n\n
To remove all documents from a collection, use an empty query with deleteMany():<\/p>\n\n\n\n
js<\/p>\n\n\n\n
CopyEdit<\/p>\n\n\n\n
db.students.deleteMany({})<\/p>\n\n\n\n
This deletes every document<\/strong> in the “students” collection. Use with caution.<\/p>\n\n\n\n To delete an entire collection (not just its documents), use:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.drop()<\/p>\n\n\n\n This permanently removes the “students” collection and all its documents.<\/p>\n\n\n\n Just like insert and update operations, deletion in MongoDB supports write concern options for durability and acknowledgment:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.deleteOne(<\/p>\n\n\n\n { name: “Alice” },<\/p>\n\n\n\n { writeConcern: { w: “majority”, wtimeout: 5000 } }<\/p>\n\n\n\n )<\/p>\n\n\n\n This ensures the delete operation is acknowledged by a majority of replica set members.<\/p>\n\n\n\n You can delete documents using the special _id field, which is typically an ObjectId:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.deleteOne({ _id: ObjectId(“5f8d0d55b54764421b7156c2”) })<\/p>\n\n\n\n This deletes the document with the specified _id.<\/p>\n\n\n\n Delete methods return an object with details:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n {<\/p>\n\n\n\n acknowledged: true,<\/p>\n\n\n\n deletedCount: 1<\/p>\n\n\n\n }<\/p>\n\n\n\n This helps verify whether documents were actually deleted and how many matched the criteria.<\/p>\n\n\n\n Using precise filters helps avoid unintended changes or deletions. Vague or empty filters may modify or delete more data than expected.<\/p>\n\n\n\n Bad:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.deleteMany({})<\/p>\n\n\n\n Good:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.deleteMany({ status: “inactive” })<\/p>\n\n\n\n Before performing a delete operation, it\u2019s a good idea to preview affected documents using a find() query:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.find({ status: “inactive” })<\/p>\n\n\n\n This helps ensure the correct documents are targeted.<\/p>\n\n\n\n In critical applications, use transactions to group multiple operations, such as update followed by delete, to ensure consistency:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n const session = db.getMongo().startSession()<\/p>\n\n\n\n session.startTransaction()<\/p>\n\n\n\n try {<\/p>\n\n\n\n db.students.updateOne({ name: “John” }, { $set: { status: “graduated” } }, { session })<\/p>\n\n\n\n db.students.deleteOne({ name: “John”, status: “graduated” }, { session })<\/p>\n\n\n\n session.commitTransaction()<\/p>\n\n\n\n } catch (e) {<\/p>\n\n\n\n session.abortTransaction()<\/p>\n\n\n\n }<\/p>\n\n\n\n Make sure that the fields used in filters for update and delete operations are indexed to improve performance, especially for large datasets.<\/p>\n\n\n\n Example:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.createIndex({ name: 1 })<\/p>\n\n\n\n This speeds up queries like:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.updateOne({ name: “Alice” }, { $set: { status: “active” } })<\/p>\n\n\n\n While upsert is powerful, it can lead to unintended document creation if filters are too broad or misconfigured. Always review upsert filters carefully.<\/p>\n\n\n\n The Update and Delete operations in MongoDB are powerful tools for managing data lifecycle. They allow you to modify existing documents, remove outdated entries, and maintain the integrity and accuracy of your database. With features like conditional updates, array filters, upserts, and write concerns, MongoDB provides a highly flexible and robust environment for data manipulation. However, with great power comes great responsibility\u2014always use precise filters, validate your operations beforehand, and employ transactions when consistency is critical. Mastery of these operations, combined with proper indexing and best practices, will help you build efficient and reliable applications that take full advantage of MongoDB\u2019s capabilities.<\/p>\n\n\n\n MongoDB allows you to perform multiple write operations in a single command using the bulkWrite() method. This can include inserts, updates, deletes, and replaces, making it efficient for batch processing.<\/p>\n\n\n\n Syntax Example:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.bulkWrite([<\/p>\n\n\n\n { insertOne: { document: { name: “Eve”, age: 20 } } },<\/p>\n\n\n\n { updateOne: { filter: { name: “Alice” }, update: { $set: { status: “graduated” } } } },<\/p>\n\n\n\n { deleteOne: { filter: { name: “Bob” } } }<\/p>\n\n\n\n ])<\/p>\n\n\n\n This command performs three operations in sequence: an insert, an update, and a delete.<\/p>\n\n\n\n MongoDB\u2019s Aggregation Framework is a powerful tool that allows you to process data and return computed results. While not strictly part of basic CRUD, it enhances read operations and can be used for tasks like filtering, grouping, and transforming data.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.aggregate([<\/p>\n\n\n\n { $match: { course: “Math” } },<\/p>\n\n\n\n { $group: { _id: “$status”, total: { $sum: 1 } } }<\/p>\n\n\n\n ])<\/p>\n\n\n\n This aggregates students by their status field and counts how many students have each status.<\/p>\n\n\n\n MongoDB supports multi-document transactions in replica sets and sharded clusters. This is useful when performing CRUD operations that must be atomic.<\/p>\n\n\n\n Transaction Example:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n const session = db.getMongo().startSession()<\/p>\n\n\n\n session.startTransaction()<\/p>\n\n\n\n try {<\/p>\n\n\n\n db.accounts.updateOne({ _id: 1 }, { $inc: { balance: -100 } }, { session })<\/p>\n\n\n\n db.accounts.updateOne({ _id: 2 }, { $inc: { balance: 100 } }, { session })<\/p>\n\n\n\n session.commitTransaction()<\/p>\n\n\n\n } catch (error) {<\/p>\n\n\n\n session.abortTransaction()<\/p>\n\n\n\n }<\/p>\n\n\n\n In this example, money is transferred between two accounts. If one update fails, the transaction is rolled back.<\/p>\n\n\n\n Change streams allow applications to listen to real-time changes in MongoDB collections. This is helpful for syncing data or triggering actions when documents are created, updated, or deleted.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n const changeStream = db.students.watch()<\/p>\n\n\n\n changeStream.on(“change”, (next) => {<\/p>\n\n\n\n printjson(next)<\/p>\n\n\n\n })<\/p>\n\n\n\n This sets up a listener for all changes to the students collection.<\/p>\n\n\n\n Mongoose is a popular Object Data Modeling (ODM) library for MongoDB and Node.js. It provides a higher-level abstraction over MongoDB and supports schema-based data modeling, validation, middleware, and more. Using Mongoose simplifies the process of writing CRUD operations in Node.js applications.<\/p>\n\n\n\n To use Mongoose, you first define a schema and then create a model.<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n const mongoose = require(“mongoose”)<\/p>\n\n\n\n const studentSchema = new mongoose.Schema({<\/p>\n\n\n\n name: String,<\/p>\n\n\n\n age: Number,<\/p>\n\n\n\n course: String,<\/p>\n\n\n\n status: String<\/p>\n\n\n\n })<\/p>\n\n\n\n const Student = mongoose.model(“Student”, studentSchema)<\/p>\n\n\n\n Now you can use the Student model to perform CRUD operations.<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n const student = new Student({<\/p>\n\n\n\n name: “Anna”,<\/p>\n\n\n\n age: 21,<\/p>\n\n\n\n course: “Engineering”,<\/p>\n\n\n\n status: “active”<\/p>\n\n\n\n })<\/p>\n\n\n\n student.save()<\/p>\n\n\n\n .then(doc => console.log(doc))<\/p>\n\n\n\n .catch(err => console.error(err))<\/p>\n\n\n\n This creates a new document and saves it to the MongoDB database.<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n Student.find({ status: “active” })<\/p>\n\n\n\n .then(docs => console.log(docs))<\/p>\n\n\n\n .catch(err => console.error(err))<\/p>\n\n\n\n Use find(), findOne(), or findById() to query documents.<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n Student.updateOne({ name: “Anna” }, { age: 22 })<\/p>\n\n\n\n .then(result => console.log(result))<\/p>\n\n\n\n .catch(err => console.error(err))<\/p>\n\n\n\n You can also use findByIdAndUpdate() or updateMany().<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n Student.deleteOne({ name: “Anna” })<\/p>\n\n\n\n .then(result => console.log(result))<\/p>\n\n\n\n .catch(err => console.error(err))<\/p>\n\n\n\n Mongoose also supports findByIdAndDelete() and deleteMany().<\/p>\n\n\n\n Mongoose allows middleware (also called pre and post hooks) for CRUD operations.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n studentSchema.pre(“save”, function (next) {<\/p>\n\n\n\n console.log(“A student is about to be saved:”, this)<\/p>\n\n\n\n next()<\/p>\n\n\n\n })<\/p>\n\n\n\n This hook runs before any document is saved.<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n User.create({ username: “john123”, password: “hashed_pw” })<\/p>\n\n\n\n User.findOne({ username: “john123” })<\/p>\n\n\n\n User.updateOne({ username: “john123” }, { email: “john@example.com” })<\/p>\n\n\n\n User.deleteOne({ username: “john123” })<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n Product.create({ name: “Laptop”, price: 999, stock: 10 })<\/p>\n\n\n\n Product.find({ price: { $lt: 500 } })<\/p>\n\n\n\n Product.updateOne({ name: “Laptop” }, { $inc: { stock: -1 } })<\/p>\n\n\n\n Product.deleteOne({ name: “Old Laptop” })<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n BlogPost.create({ title: “My First Blog”, content: “…” })<\/p>\n\n\n\n BlogPost.find({ author: “alice” })<\/p>\n\n\n\n BlogPost.updateOne({ title: “My First Blog” }, { content: “Updated content…” })<\/p>\n\n\n\n BlogPost.deleteOne({ title: “My First Blog” })<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n Inventory.create({ item: “Apples”, quantity: 100 })<\/p>\n\n\n\n Inventory.find({ quantity: { $lt: 10 } })<\/p>\n\n\n\n Inventory.updateOne({ item: “Apples” }, { $inc: { quantity: -5 } })<\/p>\n\n\n\n Inventory.deleteMany({ expired: true })<\/p>\n\n\n\n Use schema validation (with Mongoose or MongoDB\u2019s built-in validators) to ensure data integrity.<\/p>\n\n\n\n CRUD operations on large collections should use indexes to ensure fast query performance.<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.createIndex({ name: 1 })<\/p>\n\n\n\n MongoDB Atlas provides a UI to monitor query performance and track CRUD operations in real time. Use this to detect slow queries and optimize them.<\/p>\n\n\n\n In mission-critical applications, enable automatic backups and use transactions for multi-step operations to prevent data corruption.<\/p>\n\n\n\n While MongoDB is immune to SQL injection, always sanitize input to prevent NoSQL injection and misuse.<\/p>\n\n\n\n Security is critical when performing CRUD operations, especially when sensitive data like user profiles, financial records, or private documents is involved. MongoDB offers several security features to help safeguard CRUD activities, including role-based access control (RBAC), authentication, network access rules, and encryption.<\/p>\n\n\n\n MongoDB supports authentication to verify users and authorization to control what they can do.<\/p>\n\n\n\n Enable Authentication<\/strong> in the configuration file:<\/p>\n\n\n\n yaml<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n security:<\/p>\n\n\n\n authorization: “enabled”<\/p>\n\n\n\n Then create a user:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n use admin<\/p>\n\n\n\n db.createUser({<\/p>\n\n\n\n user: “appAdmin”,<\/p>\n\n\n\n pwd: “securePass123”,<\/p>\n\n\n\n roles: [{ role: “readWrite”, db: “appDB” }]<\/p>\n\n\n\n })<\/p>\n\n\n\n This ensures the user can only read and write in the appDB database.<\/p>\n\n\n\n MongoDB uses RBAC to assign privileges to users. Built-in roles include:<\/p>\n\n\n\n Example \u2013 Creating a read-only user:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.createUser({<\/p>\n\n\n\n user: “readonlyUser”,<\/p>\n\n\n\n pwd: “readonly123”,<\/p>\n\n\n\n roles: [{ role: “read”, db: “appDB” }]<\/p>\n\n\n\n })<\/p>\n\n\n\n This user can perform read operations only\u2014no inserts, updates, or deletes.<\/p>\n\n\n\n Limit which IP addresses can connect to your MongoDB instance, especially in production environments.<\/p>\n\n\n\n For MongoDB Atlas:<\/p>\n\n\n\n For self-hosted setups, bind to specific IPs only:<\/p>\n\n\n\n yaml<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n net:<\/p>\n\n\n\n bindIp: 127.0.0.1,192.168.1.10<\/p>\n\n\n\n Although MongoDB doesn’t provide built-in field-level access control, you can implement this at the application level by projecting only allowed fields:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.users.find({}, { password: 0, ssn: 0 })<\/p>\n\n\n\n This query excludes sensitive fields from the output.<\/p>\n\n\n\n Just like SQL injection, NoSQL injection can occur if user input is passed directly into queries.<\/p>\n\n\n\n Unsafe:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.users.find({ username: req.query.username })<\/p>\n\n\n\n Safe:<\/strong><\/p>\n\n\n\n Use input validation and type checks, or sanitize input with libraries such as express-validator (Node.js).<\/p>\n\n\n\n Indexes speed up read and update\/delete queries by avoiding full collection scans.<\/p>\n\n\n\n Create an index:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.createIndex({ name: 1 })<\/p>\n\n\n\n Use compound indexes<\/strong> for multi-field filtering:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.orders.createIndex({ customerId: 1, date: -1 })<\/p>\n\n\n\n Limit returned fields using projections to improve performance:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.users.find({}, { name: 1, email: 1, _id: 0 })<\/p>\n\n\n\n This prevents the transfer of large unnecessary fields like profile pictures or logs.<\/p>\n\n\n\n Avoid inserting or updating documents one by one when dealing with large datasets. Use insertMany() or bulkWrite() to batch operations:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.products.insertMany([<\/p>\n\n\n\n { name: “item1” },<\/p>\n\n\n\n { name: “item2” },<\/p>\n\n\n\n { name: “item3” }<\/p>\n\n\n\n ])<\/p>\n\n\n\n To understand how MongoDB executes a query:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.students.find({ age: 22 }).explain(“executionStats”)<\/p>\n\n\n\n This provides insight into query performance and suggests index usage.<\/p>\n\n\n\n Avoid creating documents with excessive nesting or size (MongoDB\u2019s max BSON document size is 16MB). Split complex structures into separate collections when needed.<\/p>\n\n\n\n In application code, especially in Node.js or Python, ensure that you reuse database connections rather than creating new ones for every request.<\/p>\n\n\n\n For massive datasets, enable sharding<\/strong> to distribute the collection across multiple servers:<\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n sh.enableSharding(“appDB”)<\/p>\n\n\n\n sh.shardCollection(“appDB.orders”, { customerId: 1 })<\/p>\n\n\n\n Sharding helps maintain CRUD performance even at scale.<\/p>\n\n\n\n Always provide a filter for updateMany() or deleteMany() operations. A missing or empty filter may modify or delete every document in the collection.<\/p>\n\n\n\n Risky:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.users.deleteMany({})<\/p>\n\n\n\n Safe:<\/strong><\/p>\n\n\n\n js<\/p>\n\n\n\n CopyEdit<\/p>\n\n\n\n db.users.deleteMany({ status: “inactive” })<\/p>\n\n\n\nDeleting a Collection<\/strong><\/h3>\n\n\n\n
Write Concern for Deletion<\/strong><\/h3>\n\n\n\n
Deleting by ObjectId<\/strong><\/h3>\n\n\n\n
Checking Results of Delete Operations<\/strong><\/h3>\n\n\n\n
Best Practices for Update and Delete Operations<\/strong><\/h2>\n\n\n\n
Always Use Precise Filters<\/strong><\/h3>\n\n\n\n
Use Projections to Validate Before Deleting<\/strong><\/h3>\n\n\n\n
Use Transactions for Safety<\/strong><\/h3>\n\n\n\n
Use Indexes to Optimize Updates and Deletes<\/strong><\/h3>\n\n\n\n
Avoid Overuse of Upserts<\/strong><\/h3>\n\n\n\n
Advanced CRUD Techniques in MongoDB<\/strong><\/h2>\n\n\n\n
Bulk Write Operations<\/strong><\/h3>\n\n\n\n
Using Aggregation with CRUD<\/strong><\/h3>\n\n\n\n
Transactions for Multi-Document Consistency<\/strong><\/h3>\n\n\n\n
Change Streams<\/strong><\/h3>\n\n\n\n
CRUD Operations with Mongoose (Node.js)<\/strong><\/h2>\n\n\n\n
What is Mongoose?<\/strong><\/h3>\n\n\n\n
Defining a Schema and Model<\/strong><\/h3>\n\n\n\n
Creating a Document with Mongoose<\/strong><\/h3>\n\n\n\n
Reading Documents with Mongoose<\/strong><\/h3>\n\n\n\n
Updating Documents with Mongoose<\/strong><\/h3>\n\n\n\n
Deleting Documents with Mongoose<\/strong><\/h3>\n\n\n\n
Using Mongoose Middleware<\/strong><\/h3>\n\n\n\n
Practical Use Cases of CRUD Operations<\/strong><\/h2>\n\n\n\n
User Management System<\/strong><\/h3>\n\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ul>\n\n\n\nE-commerce Product Catalog<\/strong><\/h3>\n\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ul>\n\n\n\nBlogging Platform<\/strong><\/h3>\n\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ul>\n\n\n\nInventory Management<\/strong><\/h3>\n\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ul>\n\n\n\nTips for Working with MongoDB CRUD in Production<\/strong><\/h2>\n\n\n\n
Validate Data Before Inserting or Updating<\/strong><\/h3>\n\n\n\n
Use Indexes to Optimize Performance<\/strong><\/h3>\n\n\n\n
Monitor CRUD Usage with MongoDB Atlas<\/strong><\/h3>\n\n\n\n
Automate Backups and Use Transactions Where Needed<\/strong><\/h3>\n\n\n\n
Sanitize Input to Prevent Injection<\/strong><\/h3>\n\n\n\n
CRUD Security in MongoDB<\/strong><\/h2>\n\n\n\n
Importance of Securing CRUD Operations<\/strong><\/h3>\n\n\n\n
Authentication and Authorization<\/strong><\/h3>\n\n\n\n
Role-Based Access Control (RBAC)<\/strong><\/h3>\n\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ul>\n\n\n\nIP Whitelisting and Network Security<\/strong><\/h3>\n\n\n\n
\n
<\/li>\n<\/ul>\n\n\n\nField-Level Redaction and Access Control<\/strong><\/h3>\n\n\n\n
Preventing NoSQL Injection<\/strong><\/h3>\n\n\n\n
Performance Optimization for CRUD Operations<\/strong><\/h2>\n\n\n\n
Use Indexes Wisely<\/strong><\/h3>\n\n\n\n
Use Projections in Read Operations<\/strong><\/h3>\n\n\n\n
Use Batching for Writes<\/strong><\/h3>\n\n\n\n
Use <\/strong>explain()<\/strong> to Analyze Query Plans<\/strong><\/h3>\n\n\n\n
Limit Document Size and Nesting<\/strong><\/h3>\n\n\n\n
Leverage Connection Pooling<\/strong><\/h3>\n\n\n\n
Sharding for Scalability<\/strong><\/h3>\n\n\n\n
Common CRUD Pitfalls to Avoid<\/strong><\/h2>\n\n\n\n
Forgetting to Use Filters in Updates and Deletes<\/strong><\/h3>\n\n\n\n
Overusing Upserts<\/strong><\/h3>\n\n\n\n