Skip to main content

Dotnet Core Basic CRUD Operations With MongoDB Using Repository Pattern


Introduction:
MongoDB is a document-oriented database, which is classified as a NoSQL database. In MongoDB, tables are called collections and records are called documents. It stores data in JSON format. The reading of data from MongoDB is fast when compared to the Relational Database. But MongoDB doesn't have a relation between the collections. We can't declare NoSQL is better than SQL or vice-versa. So depending on the application requirement either select NoSQL or SQL or Both database.

Dotnet Core by default uses an MSSQL database, but it has built-in support for all other types of datastores like MYSQL, ORACLE, and MongoDB, etc.

Step 1:
Click here to install the MongoDB community edition. After successful installation go to "C:\Program Files\MongoDB\Server\4.2\bin" and then run "mongod.exe". Now we started MongoDB server in our local machine on a default port 27017.

Step 2:
Now open MongoDB shell command "mongo.exe" which is found in "C:\Program Files\MongoDB\Server\4.2\bin", where we can execute database queries.

Step 3:
Now create a database name as "MyWorldDatabase" using the following command "use MyWorldDatabase" in mongo.exe command. If the database already exists it will use existing or else creates a new database with that name on adding a document in a collection for the first time.

Step 4:
Create a collection name as "LivingCreatures", using the command "db.createCollection('LivingCreatures')"

Step 5:
In MongoDB records or data called as documents. So Adding document to MongoDB can be done with commands "db.collectionName.insertOne()" for one document insertion and "db.collectionName.insertMany()" for mutiple document insertion. Add the following test documents into "LivingCreatures" collection
 [
    {
      "CreatureName": "Human Being",
      "Home": "Land",
      "Category": "Omnivores",
      "Description": "Eats both plants and flesh of other animals"
    },
    {
      "CreatureName": "Lion",
      "Home": "Land",
      "Category": "Carnivores",
      "Description": "Eats flesh of other animals"
    },
    {
      "CreatureName": "Tiger",
      "Home": "Land",
      "Category": "Carnivores",
      "Description": "Eats flesh of other animals"
    },
    {
      "CreatureName": "Bear",
      "Home": "Land",
      "Category": "Omnivores",
      "Description": "Eats both plants and flesh of other animals"
    },
    {
      "CreatureName": "Goat",
      "Home": "Land",
      "Category": "Herbivores",
      "Description": "Eats plants"
    }
  ]


now to see all the documents use the command "db.LivingCreatures.find({}).pretty()", here pretty() extention function to display output in good format.


Step 6:
Create a Dotnet Core Web API project, click here. "Install-Package MongoDB.Driver.Core -Version 2.9.1" this NuGet provides all helper methods to access MongoDB.

Step 7:
Now add "Models" folder in web API project. Add class and name as "LivingCreature" which represents our collection in the database
  namespace MongoDBSample1.Model
{
    public class LivingCreature
    {
        [BsonId]
        [BsonRepresentation(BsonType.ObjectId)]
        public string Id { get; set; }
        public string CreatureName { get; set; }
        public string Home { get; set; }
        public string Description { get; set; }
      public string Category { get; set; }
    }
}

. "BsonId" attribute represents the primary key in the document.
. "BsonRepresentation(BsonType.ObjectId)" attribute to assign as a string instead of an object from document primary key which is auto-generated in MongoDB.

Step 8:
Update the "appsettings.json" with the following configurations

. "ConnectionString" contains MongoDB connection string
. "DatabaseName" name of the databse
. "LivingCreatureCollection" name of the collection

Step 9:
In "Models" add a class name as "AppSetting.cs" which contains all configuration properties
  namespace MongoDBSample1.Model
{
    public class AppSettings
    {
        public string LivingCreatureCollection { get; set; }
        public string ConnectionString { get; set; }
        public string DatabaseName { get; set; }
    }
}

Step 10:
Now configure "AppSetting.cs" in application "startup.cs" file. In "startup.cs" file, go to "ConfigureServices" method add the following line of code
  services.Configure(Configuration.GetSection(nameof(AppSettings)));
Now "AppSetting.cs" can be accessed with "Microsoft.Extensions.Options.IOptions<T>" in any class by dependency injction.

Step 11:
Add a new folder name as "Data". In the "Data" folder add a class name as "MyWorldContext" which holds MongoDB client that interacts with a database.

IMyWorldContext.cs:

 namespace MongoDBSample1.Data
{
    public interface IMyWorldContext
    {
        IMongoDatabase MyWorldDb { get; }
    }
} 

MyWorldContext.cs:
  namespace MongoDBSample1.Data
{
    public class MyWorldContext: IMyWorldContext
    {
        public   IMongoDatabase MyWorldDb { get; set; }

        public MyWorldContext(IOptions<appsettings> options)
        {
            var mongoClient = new MongoClient(options.Value.ConnectionString);
            MyWorldDb = mongoClient.GetDatabase(options.Value.DatabaseName);
        }
    }
}

."MongoDB.Driver.MongoClient" creates an instance to communicate with MongoDB server.
. "mongoClient.GetDatabase("Name_Of_The_Database")" provides access to the required database

Now MyWorldContext needs to be registered for dependency injection in the "ConfigureServices()" method in "startup.cs" file.
  services.AddSingleton<IMyWorldContext, MyWorldContext>();

." AddSingleton()" means objects get created on application start and lives until the application stop, like one-time creation. MongoClient to be initialized one time, so context class registered for singleton scope.

Step 12:
Create a folder name as "Repos" and add a file name as "LivingCreatureRepository.cs" which do all CRUD operations on "LivingCreatures" collection

ILivingCreatureRepository.cs:
  namespace MongoDBSample1.Repos
{
    public interface ILivingCreatureRepository
    {
        Task<IList<LivingCreature>> GetAll();
    }
}

LivingCreatureRepository.cs:
  namespace MongoDBSample1.Repos
{
    public class LivingCreatureRepository:ILivingCreatureRepository
    {
        private readonly IMongoCollection<LivingCreature> _livingCreatreCollction;
        public LivingCreatureRepository(IOptions<AppSettings> options, IMyWorldContext myWorldContext)
        {
            _livingCreatreCollction = myWorldContext.MyWorldDb.GetCollection<LivingCreature>(options.Value.LivingCreatureCollection);
        }

        public async Task<IList<LivingCreature>> GetAll()
        {
            return await _livingCreatreCollction.Find(_ => true).ToListAsync();
        }
    }
}

. "IMongoCollection" holds "LivingCreatures" collection
. "_livingCreatureCollection.find()" gets the documents matches, to get all document give "true" in find() method which returns all documents from the "LivingCreatures" collection.

Now to inject this "LivingCreaturesRepositry" register in "startup.cs" file. Add the following line "configureService()" method
  services.AddScoped<ILivingCreatureRepository, LivingCreatureRepository>();

. "AddScoped()" repository instance gets created per request.

Step 13:
Create a controller name as "LivingCreatureController.cs", add action method to get all the "LivingCreatures".
 namespace MongoDBSample1.Controllers
{
    [Route("api/[controller]")]
    [ApiController]
    public class LivingCreatureController : ControllerBase
    {
        private readonly ILivingCreatureRepository _livingCreatureRepository;

        public LivingCreatureController(ILivingCreatureRepository livingCreatureRepository)
        {
            _livingCreatureRepository = livingCreatureRepository;
        }

        [HttpGet]
        [Route("all")]
        public async Task<IActionResult> GetAll()
        {
            return Ok(await _livingCreatureRepository.GetAll());
        }
    }
}

now run the web API and navigate to "https://localhost:44358/api/LivingCreature/all"

Step 14:
Now we need to add logic to create a new document to "LivingCreatures" collection. Update the
"LivingCreatureRepository.cs" with the following method.

ILivingCreatureRepository.cs:
 Task AddCreature(LivingCreature creature);

LivingCreatureRepository.cs:
   public async Task AddCreature(LivingCreature creature)
        {
            await  _livingCreatreCollction.InsertOneAsync(creature);
        }

. "_livingCreaterCollection.InsertOneAsync()" adds new document to collection

Now add action method to the controller  as below
     [HttpPost]
        [Route("add")]
        public async Task Create(LivingCreature creature)
        {
            await _livingCreatureRepository.AddCreature(creature);
            return Ok();
        }

To test this endpoint browser directly don't support the "POST" action, use google postman or fiddler to test the post endpoint as below

To check the newly added document, once again navigate to get endpoint above.

Step 15:
Update a document in the collection by using dotnet helper methods like "MongoDB.Driver.ReplaceOneAsync(_filter_expresion,_document_tobeUpdated)", based on filter expression, matching record get update.

Add below code to repository

ILivingCreatureRepository.cs:
  Task Update(LivingCreature creature);
LivingCreatureRepository.cs:
   public async Task Update(LivingCreature creature)
        {
            await _livingCreatreCollction.ReplaceOneAsync(_ => _.Id == creature.Id, creature);
        }

Add update action method in controller as below
  [HttpPost]
        [Route("update")]
        public async Task Update(LivingCreature creature)
        {
            await _livingCreatureRepository.Update(creature);
            return Ok();
        }

Test it using postman as below

Step 16:
Delete a document in the collection by using dotnet helper methods like "MongoDB.Driver.DeleteOneAsync(id)", based on id of a document, matching document get deleted.

ILivingCreatureRepository.cs:
  Task Delete(string id);
LivingCreatureRepository.cs:
   public async Task Delete(string id)
        {
            await _livingCreatreCollction.DeleteOneAsync(_ => _.Id == id);
        }
Controller:
  [HttpDelete]
        [Route("delete")]
        public async Task Delete(string id)
        {
            await _livingCreatureRepository.Delete(id);
            return Ok();
        }

Support Me!
Buy Me A Coffee PayPal Me 

Comments

  1. same thing i had done but its not entering into the controller ,it shows 404 error....
    why?????

    ReplyDelete
    Replies
    1. Hi Kavya,
      404 means unable to found your end point(API url)
      cross check your end point

      Delete

Post a Comment

Popular posts from this blog

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update data for their respective clients. Some of the Key Characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-ONly cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use the authentication with HTTP-only JWT cookie then we no need to implement the custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually