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

## Why Choose NoSQL?

There are two main reasons why engineers choose NoSQL databases for their problems:

* #### Minimizing the Impedance Mismatch 

   Since a lot of effort is spent on mapping in-memory to in-database, saving that effort improves developer productivity.

   Sometimes, a NoSQL database has a data model that better suits the needs of our application, and thus simplifies the interaction of the application code with the database. This way, we have less code to develop and maintain. 

  For example, in *MEAN stack* (M is for Mongo DB) the whole stack uses JSON objects, and the interaction of application code and database is minimal.

* #### Embracing large scale data 

  Today it is very time-consuming to store a large amount of data in the relational databases. Businesses have a need to capture and process a lot of data more quickly because many NoSQL databases are designed to run on clusters, which are a better fit for this kind of problem. 
 
  Large scale clusters give us the ability to store larger data sets and process large amounts of analytic data. Also, NoSQL databases have different data models that may be better for processing huge amounts of data.

# Why Choose NoSQL?

There are two main reasons why engineers choose NoSQL databases for their problems:

* #### Minimizing the Impedance Mismatch 

   Since a lot of effort is spent on mapping in-memory to in-database, saving that effort improves developer productivity.

   Sometimes, a NoSQL database has a data model that better suits the needs of our application, and thus simplifies the interaction of the application code with the database. This way, we have less code to develop and maintain. 

  For example, in *MEAN stack* (M is for Mongo DB) the whole stack uses JSON objects, and the interaction of application code and database is minimal.

* #### Embracing large scale data 

  Today it is very time-consuming to store a large amount of data in the relational databases. Businesses have a need to capture and process a lot of data more quickly because many NoSQL databases are designed to run on clusters, which are a better fit for this kind of problem. 
 
  Large scale clusters give us the ability to store larger data sets and process large amounts of analytic data. Also, NoSQL databases have different data models that may be better for processing huge amounts of data.

This lesson explains the reasons why NoSQL is chosen by engineers-- it touches on the concept of Polyglot Persistence.

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

Polyglot Persistence

Why Choose NoSQL?

Minimizing the Impedance Mismatch