Mongo.tar.gz

Random

RunFrontEnd

RunBackEnd

CSharpTest

RunProject

RunMiniPro

RunMiniPro2

RunMiniPro3

RunMiniPro4

CSharpExecutables

TestingFile

ReadUsers

UpdateUsers

DeleteUsers

MongoDB has quickly become the foremost NoSQL database on the market, having been adopted by companies of all sizes for the various benefits it offers toward building modern applications. In this interactive course, you'll get to see for yourself why there's so much hype around MongoDB, and learn all about how to use it.

You'll start off with an introduction to Relational and NoSQL databases, get into some basic command operations, and build up from there toward more advanced concepts. You'll then get into using MongoDB in C# and .NET Core as well as its uses in MEAN Stack. Throughout the way, you'll have the chance to use MongoDB to build interesting projects as you learn.

The Definitive Guide to MongoDB

In the [previous](https://www.educative.io/courses/definitive-guide-to-mongodb/front-end-infrastructure-implementation) lesson, we discussed the frontend infrastructure. Now, let's look at the back-end.
## model Folder
In this [project](https://github.com/NMZivkovic/MEANStackCrashCourse), you will find the directory *mean_backend*. If you look into it, you'll see that there is a *user model* defined on the back-end as well (`/model/user.js` file). 

Here, is where the library **Mongoose** comes into play. This library is used to simplify validations, castings, and business logic that revolves around database access to MongoDB. There is a folder *model* on the back-end implementation too, but this one is a bit more complicated since it contains a database access layer as well. 

This is what it looks like:

In the [previous](https://www.educative.io/courses/definitive-guide-to-mongodb/front-end-infrastructure-implementation) lesson, we discussed the frontend infrastructure. Now, let's look at the back-end.
# model Folder
In this [project](https://github.com/NMZivkovic/MEANStackCrashCourse), you will find the directory *mean_backend*. If you look into it, you'll see that there is a *user model* defined on the back-end as well (`/model/user.js` file). 

Here, is where the library **Mongoose** comes into play. This library is used to simplify validations, castings, and business logic that revolves around database access to MongoDB. There is a folder *model* on the back-end implementation too, but this one is a bit more complicated since it contains a database access layer as well. 

This is what it looks like:

This lesson explains the back-end infrastructure implementation, the model's folder, the working of mongoose, and the user.js file.

Back-End Infrastructure Implementation

Introduction to NoSQL and Polyglot Persistence

Getting Started Using MongoDB

High Availability and High-Throughput Configurations

Using MongoDB in C# and .Net Core

Using MongoDB with Node.js, Express and Angular

Serverless & MongoDB Atlas

Appendix

Back-End Infrastructure Implementation

model Folder