Give me a bird's eye view of MVC architecture

Can someone give me a bird's eye view of the MVC (Model-View-Controller) architecture typically used in software design? I've been looking for simpler definitions online but looks like people need large paragraphs of text to explain it.

Would appreciate a brief, to-the-point explanation.

Replies

Welcome, guest

Join CrazyEngineers to reply, ask questions, and participate in conversations.

CrazyEngineers powered by Jatra Community Platform

  • Anoop Kumar

    @anoop-kumar-GDGRCn • May 14, 2012

    View : front page, it just recieve the data from backend and show it.
    Controller: only redirect which request should go, a router between view and model which manages session also.
    Model: recieve *commands* from view, what to do,implement besiness logic, communicate to database.

  • Kaustubh Katdare

    @thebigk • May 14, 2012

    Thanks, #-Link-Snipped-#

  • sookie

    @sookie-T06sFW • May 29, 2012

    ianoopModel: recieve *commands* from view, what to do,implement besiness logic, communicate to database.

    Correction here according to me(Please correct me if wrong!)
    Model do not receive any commands from view. It just consists of data fetched from database or from view. For e.g If you have a Form type page then data user enters in the page is binded in the request and sent to the database in the form of a Model and similarly if I have a page that display's users details from the database then these details are fetched from the database and sent to the "View" as a "Model". Hence in short "Model" is just an entity that represents the data.

  • Anoop Kumar

    @anoop-kumar-GDGRCn • May 29, 2012

    Yes, the model didn't recieves commands from view. I was meaning that, it implements business logic what a user wants, models data and respond.
    the main purpose of MVC is saparating layers of presentation layer , controller layer and implementation layer.

  • Kaustubh Katdare

    @thebigk • May 29, 2012

    Thanks, that makes more sense now.