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

## Introduction
Today we are facing a rapid expansion of data-driven businesses, especially businesses that are web-based and have an enormous amount of data being transferred every second. In fact, almost [90%](https://www.forbes.com/sites/bernardmarr/2018/05/21/how-much-data-do-we-create-every-day-the-mind-blowing-stats-everyone-should-read/#31c0ce8c60ba) of all data on the web has been created in the last several years. Usually this data has to be stored in a *database*. However, since every business is different, there are different needs that need to be taken into account when looking at ways to store the data. There are two routes we can take: 

* *Relational Databases*
* *NoSQL*

Further on, you will cover the strengths and weaknesses of both, but it will largely focus on  *NoSQL* databases and why we need to consider them as a solution to our problems.

## Relational Databases

The concept of relational database concept was first proposed in 1970 by Edgar F. Codd and has been ruling our world since the mid-1980s. Somewhere in the ’90s concepts like Object Databases threatened to take reign, but that never happened. There are many reasons why people love relational databases and why they have been so dominant for such a long time.

## Why Use Relational Databases?

* Firstly, they are very close to the way we see the world. The entities in the application domain are modeled naturally using *records* and *tables*. Relationships between these tables are created based on the relationships that exist between the corresponding entities in the application domain. 


* *Relational databases* also have strong consistency, meaning that once a change is made to some of the records, it can be seen by every application in that domain. This made relational databases an ideal integration mechanism, with multiple applications sharing a common database and data.


* *Relational databases* have the *Transactions* feature. This gives us a way to assign changes to multiple tables and roll back previous changes, in case one instruction fails. This is a fairly complex, but powerful, feature used in data-intensive systems to provide stability.

* They have the *Joins* feature.

 
* *SQL* has pretty much become the standard language for a wide range of *relational databases*. And since it is very expressive and easy to learn, this made it more accessible to relational databases. Hence, SQL provides expressiveness to the developer.

So, to sum it up, *consistency*, *integration*, *expressiveness*, and *stability* are the reasons we can find relational databases within nearly every business solution today.

# Introduction
Today we are facing a rapid expansion of data-driven businesses, especially businesses that are web-based and have an enormous amount of data being transferred every second. In fact, almost [90%](https://www.forbes.com/sites/bernardmarr/2018/05/21/how-much-data-do-we-create-every-day-the-mind-blowing-stats-everyone-should-read/#31c0ce8c60ba) of all data on the web has been created in the last several years. Usually this data has to be stored in a *database*. However, since every business is different, there are different needs that need to be taken into account when looking at ways to store the data. There are two routes we can take: 

* *Relational Databases*
* *NoSQL*

Further on, you will cover the strengths and weaknesses of both, but it will largely focus on  *NoSQL* databases and why we need to consider them as a solution to our problems.

# Relational Databases

The concept of relational database concept was first proposed in 1970 by Edgar F. Codd and has been ruling our world since the mid-1980s. Somewhere in the ’90s concepts like Object Databases threatened to take reign, but that never happened. There are many reasons why people love relational databases and why they have been so dominant for such a long time.

# Why Use Relational Databases?

* Firstly, they are very close to the way we see the world. The entities in the application domain are modeled naturally using *records* and *tables*. Relationships between these tables are created based on the relationships that exist between the corresponding entities in the application domain. 


* *Relational databases* also have strong consistency, meaning that once a change is made to some of the records, it can be seen by every application in that domain. This made relational databases an ideal integration mechanism, with multiple applications sharing a common database and data.


* *Relational databases* have the *Transactions* feature. This gives us a way to assign changes to multiple tables and roll back previous changes, in case one instruction fails. This is a fairly complex, but powerful, feature used in data-intensive systems to provide stability.

* They have the *Joins* feature.

 
* *SQL* has pretty much become the standard language for a wide range of *relational databases*. And since it is very expressive and easy to learn, this made it more accessible to relational databases. Hence, SQL provides expressiveness to the developer.

So, to sum it up, *consistency*, *integration*, *expressiveness*, and *stability* are the reasons we can find relational databases within nearly every business solution today.

This lesson introduces relational databases; it, goes over their advantages, uses, and the problems related to them.

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

Relational Database

Introduction

Relational Databases