Discover MongoDB's rise as the leading NoSQL database. Gain insights into using it with C#/.NET Core and MEAN Stack. Delve into practical projects and advanced concepts.

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

## Modules & Components

We will be implementing the following project from [GitHub](https://github.com/NMZivkovic/MEANStackCrashCourse); so let's start by discussing the different folders/files that we'll be using throughout the project.

In the [GitHub project](https://github.com/NMZivkovic/MEANStackCrashCourse), there is a separate *mean_frontend* folder. 

You can see that there are a bunch of files in there, most of which are configuration files. Our focus should be on the *src* folder, where the source code is. This is probably a good moment to introduce the terms *Modules* and *Components*, as they are the main units of every Angular application. 


Angular applications are modular, and have their own modular system – `NgModules`. These modules help developers organize applications in blocks of functionality and to have a better separation of concerns.

Every Angular application has at least one module called the *root* module, which can be found in the project with the named – `AppModule`. Since our application is going to be a simple one, we will only use this module; you can find it in the file *app.module.ts* in the *mean_frontend/src/app/* directory. 

>Each module can have one or more Angular Component.




# Modules & Components

We will be implementing the following project from [GitHub](https://github.com/NMZivkovic/MEANStackCrashCourse); so let's start by discussing the different folders/files that we'll be using throughout the project.

In the [GitHub project](https://github.com/NMZivkovic/MEANStackCrashCourse), there is a separate *mean_frontend* folder. 

You can see that there are a bunch of files in there, most of which are configuration files. Our focus should be on the *src* folder, where the source code is. This is probably a good moment to introduce the terms *Modules* and *Components*, as they are the main units of every Angular application. 


Angular applications are modular, and have their own modular system – `NgModules`. These modules help developers organize applications in blocks of functionality and to have a better separation of concerns.

Every Angular application has at least one module called the *root* module, which can be found in the project with the named – `AppModule`. Since our application is going to be a simple one, we will only use this module; you can find it in the file *app.module.ts* in the *mean_frontend/src/app/* directory. 

>Each module can have one or more Angular Component.




This lesson explains the front-end infrastructure implementation, the modules, components, and goes over the folder structure of the project we'll go over and implement in this chapter.

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

Front-End Infrastructure Implementation

Modules & Components