The ultimate guide to coding interviews: Learn and practice JavaScript design patterns tested by FAANG engineers. Get interview-ready in just a few hours with battle-tested solutions.

If you're an experienced developer, chances are your interviewer won't ask you about language syntax. Instead, they'll focus on things that test your understanding of software architecture, and how capable you are at finding optimized solutions to given problems. 

That’s where a strong understanding of design patterns comes in handy. It's often useful to be able to draw on established patterns instead of reinventing the wheel.

In this course, you will learn how to effectively deploy design patterns to answer interview questions. The course is divided into four sections: Creational Patterns, Structural Patterns, Behavioral Patterns, and Architectural Patterns. Each section has its own set of design patterns which you’ll learn to use through various challenges. 

Every challenge contains a detailed solution explanation. By the end of this course (and with some practice), you will be able to confidently use design patterns to tackle advanced coding interview questions in JavaScript.

JavaScript Design Patterns for Coding Interviews

## What is the MVP pattern? 

The MVP pattern stands for **model view presenter**. It is derived from the MVC pattern, which focuses on the user interface.  MVP however, is focused on improving the *presentation* logic. 

It consists of three components:

* **Model:** provides the data that the application requires, which we want to display in the *view*

* **View:** to display the data from the model, it passes the user actions/commands to the presenter to act upon that data

* **Presenter:** acts as the middle man between the *model* and the *view*. Retrieves data from the *model*, manipulates it, and returns it to view for display. It also reacts to the user’s interaction with the *view*.


$$$$
### What's the difference between MVP and MVC?

| **MVC** 	| **MVP** 	|
|-------------------------------------------------------------------------------------------------------------------	|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
| The *controller* acts as the mediator between the *model* and the *view* 	| The *presenter* acts as the mediator between the *model* and the *view* 	|
| Controller can share multiple views 	| The presenter has a one to one mapping with the view. If the view is complex, it can use multiple presenters 	|
| The view can also communicate directly with the model by observing it for changes and updating itself accordingly 	| The model and the view are more separate in this pattern as the presenter reacts to user actions by retrieving and manipulating model data and returning it to the view for display |

# What is the MVP pattern? 

The MVP pattern stands for **model view presenter**. It is derived from the MVC pattern, which focuses on the user interface.  MVP however, is focused on improving the *presentation* logic. 

It consists of three components:

* **Model:** provides the data that the application requires, which we want to display in the *view*

* **View:** to display the data from the model, it passes the user actions/commands to the presenter to act upon that data

* **Presenter:** acts as the middle man between the *model* and the *view*. Retrieves data from the *model*, manipulates it, and returns it to view for display. It also reacts to the user’s interaction with the *view*.


$$$$
## What's the difference between MVP and MVC?

| **MVC** 	| **MVP** 	|
|-------------------------------------------------------------------------------------------------------------------	|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
| The *controller* acts as the mediator between the *model* and the *view* 	| The *presenter* acts as the mediator between the *model* and the *view* 	|
| Controller can share multiple views 	| The presenter has a one to one mapping with the view. If the view is complex, it can use multiple presenters 	|
| The view can also communicate directly with the model by observing it for changes and updating itself accordingly 	| The model and the view are more separate in this pattern as the presenter reacts to user actions by retrieving and manipulating model data and returning it to the view for display |

You will learn about the MVP pattern in detail with the help of a coding example in this lesson.


Before We Begin

Introduction To Design Patterns

Creational Patterns

Structural Patterns

Behavioral Patterns

Architectural Patterns

Conclusion

MVP Pattern

What is the MVP pattern?

What’s the difference between MVP and MVC?

MVC	MVP
The controller acts as the mediator between the model and the view	The presenter acts as the mediator between the model and the view
Controller can share multiple views	The presenter has a one to one mapping with the view. If the view is complex, it can use multiple presenters
The view can also communicate directly with the model by observing it for changes and updating itself accordingly	The model and the view are more separate in this pattern as the presenter reacts to user actions by retrieving and manipulating model data and returning it to the view for display