Checkout my full courses on Udemy:- 1) Spring Batch Framework for Beginners www.udemy.com/... 2) Struts 2 Framework for Beginners www.udemy.com/... 3) Java Chat Application www.udemy.com/...
I really liked how you explained it first with the colors to get the main point across, then labeled each part MVC, then got into the specific names like JSP, Servlet. Made it much easier to understand, thank you!!
I have two questions 1- does implementing different programming languages requires different architecture pattern or does it does not rely on it? 2- for my final year project, I am building a web-based application which online course platform where users can enroll in courses by paying the required price the project will be built in following technologies front end : HTML CSS JAVASCRIPT back end: Php database: MySQL my question is which architecture design is suited for my web-based application?
How can the Client send a request to the Controller without a view at the first place? They have to interact with an interface (a view) and then that view triggers the Controller, tells the Controller what the client want to read from the database, right? 🤨 🤔🤔....
In MVC pattern, I understand that always Controller is the middle man. So when a view is returned it is returned to the Controller BUT not directly to the client. Please clarify or correct the diagram.
The client sends a request e.g., a GET request to the Web Server. The Web Server passes this request to a DispatcherServlet. Think of DispatcherServlet as a front Controller (think of it like a Primary Controller). The DispatcherServlet finds the appropriate handler method defined in Controller that you as a developer has written. In the Controller method, the Model class will be called. The Model class has the Business logic to read / write data from / to database, apply transformation on data etc. The Model class will hold the data that needs to be rendered in the view. The Controller method will have a reference to the View that should be rendered when the execution finishes. When the controller method finishes executing, it returns a result (to the Web Server) which typically includes a reference to the view (such as a view name or a View object) and the model data to be displayed in the view. The Web Server then uses this information, renders the view (uses the view and model to generate an HTML page) and then it sends the rendered view back to the client as the body of the HTTP response.
User uses the browser to send the request to the server. Controller takes the request through Request Parameter and sends that request to the Model. AND model is the ones that deals with the database so it takes the request from the controller and communicates with the database and queries according the the request and sends the data back to controller. BUT the data that is sent to the controller is raw data which is not formatted so it sends the raw data to the VIEW which is responsible for formatting the data OR generating UI (HTML CSS) using the data. After formatting it sends the formatted data to the client which is the browser. This is what i learned from the video. You may already know this concept as this comment was posted 5 months ago.
@@pawanshrestha3823 Actually the Answer to my question is : User does not interact with the controller but it interact with the view (ex. HTML Page) and from the View the user makes a request to server. At server the Controller (ex. A Servlet, or RestController in Spring Boot) takes that request and send it a MODEL (ex. Java classes and api) ....
I really liked how you explained it first with the colors to get the main point across, then labeled each part MVC, then got into the specific names like JSP, Servlet. Made it much easier to understand, thank you!!
Thank you :)
This explanation is simple yet so effective. Thanks a lot!
At 4:20 you are directly sending the view arrow to the client. I think it should go through the controller, which is responsible for the response.
This is what i was also thinking, because i have watched some videos about MVC and view send data to controller and controller send data to client
That's not correct
View will directly send response to client
@@beast0726 since controller is servlet filter so reqest and response go through it
This is one of the best ways of explanation.
Thank you, dude.
Very easy to understand for beginners in MVC. Thanks a lot for the simplest explanation.
This explanation is simple yet so effective. Thanks a lot Sir!
It's very cool & Amazing 👍
Thanks, you've made the MVC concept easy to understand.
I appreciate this video as you provide real world examples. Thank you.
No words of ur best explanation. Easy understanding
Thank you so much :)
Awesome video! I love how you explain first without using names, it makes it so easy to understand. Thanks 🙏
within 5 minutes we cover this topic.
thankyou so much so grateful teaching
I was need this types of explanation that I got. ❤ Thanks brother.
Awesome Man, I hope you have such videos on other important concepts
Explained in the simplest way possible, thank you my friend
This is explained really well. Thank you.
Life saving video,best video ever, loads of ❤️ form PICT ,Pune
Today my teacher explained but I was stuck. thanks for easy explanation.
Great tutorial Abhay. Could u plz come up with MVP and MVVM designs paterns too?
Thanks. I will try to make it :)
@@abhayredkaracademy but you didn't. So sad
Thanks For the excellent explanation Sir !🎉
I have two questions
1- does implementing different programming languages requires different architecture pattern or does it does not rely on it?
2- for my final year project, I am building a web-based application which online course platform where users can enroll in courses by paying the required price the project will be built in following technologies
front end : HTML CSS JAVASCRIPT
back end: Php
database: MySQL
my question is which architecture design is suited for my web-based application?
Very easy to understand! Thank you!
great explanation using colored boxes! Thank you very muchh!
thank you so much...best video on topic,you are very good teacher.the way you explain is fantastic.keep it up.
Thanks for the comment :)
wow, nice explanation. Now I understand MVC...
Thank you :)
Thnq sir....ur way of teaching very very good ❤
what a fantastic way to teach...!!!!...keep it up bro
it's outstanding bro
Great job, THANKS, super explained!
Best explained 👍
Explained very clearly, Thank you
It was easy to understand, thanks to the tutorial.
extremely clear explanation. Thank you
Best explanation till date may Allah bless you
Very clear explanation...!!! Thanks a lot❤
Thank you very much sir it helps me alot for my today's exam❤
wow ...very good explanation...great help in understanding the MVC architecture pattern
Nice explanation
Explanation was superb
Just to the point. Thanks.
excellent tutorial
Amazing video
So easy explained for Buisness analyst 😄
Nice explanation tan q
kamal ka smjaya sir
👏💯
I really loved it liked u explained very clearly super bro awesome keep it up bro expecting more. Videos from u bri
Great tutorial... Really learnt a lot from this
Thank you :)
How can the Client send a request to the Controller without a view at the first place?
They have to interact with an interface (a view) and then that view triggers the Controller,
tells the Controller what the client want to read from the database, right? 🤨
🤔🤔....
What a beautiful explanation
Excellent explanation. Thanks!
Thank you for your video about MVC :)
Loved the explanation 🙌🙌
Thank you so much
appreciate brother its still working
sir please make video on client server architecture
In MVC pattern, I understand that always Controller is the middle man. So when a view is returned it is returned to the Controller BUT not directly to the client. Please clarify or correct the diagram.
The client sends a request e.g., a GET request to the Web Server. The Web Server passes this request to a DispatcherServlet. Think of DispatcherServlet as a front Controller (think of it like a Primary Controller). The DispatcherServlet finds the appropriate handler method defined in Controller that you as a developer has written. In the Controller method, the Model class will be called. The Model class has the Business logic to read / write data from / to database, apply transformation on data etc. The Model class will hold the data that needs to be rendered in the view. The Controller method will have a reference to the View that should be rendered when the execution finishes. When the controller method finishes executing, it returns a result (to the Web Server) which typically includes a reference to the view (such as a view name or a View object) and the model data to be displayed in the view. The Web Server then uses this information, renders the view (uses the view and model to generate an HTML page) and then it sends the rendered view back to the client as the body of the HTTP response.
crystal clear explaination
I am very stifcation you vidio sir thanks for watching this vidio
thanks bro it's really help
Very nice understanding
Superb tutorial 🙏🏻 thanks
Great explenation! Many thanks!!!
Best explanation sir....
NO COMPLICATION.......quick understanding of MVC..KIP IT UP :)
Thank you so much :)
Wow I like your explanation
Great explanation 🎉
Thank you very much sir you are awsome
Great tutorial. Explanation 👌
really helpful brother....thankyou....
Thank you :)
Awesome explanation
sweet simple on spot ❤
Very well explained ✌️👍
Thank you sir , its very helpful.
Congratulations! You gained a new subscriber 😊
Neatly explained!
Well explanation.... Superbbb❤️
very good explanation!
nicely done
Bro excellent very good great bro
very very nice explain
Nice simple and straight. Great !! Pls come up with more videos on MVP designs
Thanks a lot..🙂✨
You earned a like and subscribe.Very good explanation
Great explaination
Nice explained!!
Thank you, very helpful.
You're the best
Nicely explained 👌 👏
Nice explanation 👌
Ultimate sir ji
Thank you so much this video helped me so much ❤️
In oose also ths MVC topic they can I write ths
But the user will interact with a view (UI), how a user can interact with controller because it is just a code (as you said it is servlet) ?
User uses the browser to send the request to the server. Controller takes the request through Request Parameter and sends that request to the Model. AND model is the ones that deals with the database so it takes the request from the controller and communicates with the database and queries according the the request and sends the data back to controller. BUT the data that is sent to the controller is raw data which is not formatted so it sends the raw data to the VIEW which is responsible for formatting the data OR generating UI (HTML CSS) using the data. After formatting it sends the formatted data to the client which is the browser.
This is what i learned from the video. You may already know this concept as this comment was posted 5 months ago.
@@pawanshrestha3823 Actually the Answer to my question is : User does not interact with the controller but it interact with the view (ex. HTML Page) and from the View the user makes a request to server. At server the Controller (ex. A Servlet, or RestController in Spring Boot) takes that request and send it a MODEL (ex. Java classes and api) ....
awesome explantaion
Thanks bro❣️
thanks
very well explained my concept clear of mvc than you....
Thank you💌
Thank you sir
Awesome brother
Thank You