While the majority of the request going to Joomla end up displaying a view, this is not the case for all of them. When records are published from a backend list screen, a controller task is called to do the publishing. To handle publishing in backend tasks Joomla has specially coded controllers and models.
The most typical type of screen seen in the backend of Joomla is one that lists all the records in a table making them available for editing. Let's start off the backend of the Noida City component, with a list of all the places in the database.
Despite doing slightly different things, both the frontend and the backend of Joomla use the Model View Controller design pattern for organizing code. The biggest difference is that the frontend is primarily used for displaying data while the backend is used for managing it.
So the first difference is that you can usually get away with a single controller in the frontend, and you usually cannot get away with a single controller in the backend. In the frontend, nine times out of ten, you're just displaying a view, you're not going to have as many forms as you have in the backend and you aren't going to be taking in as many specific requests from users.
One of Joomla's strongest features is the ability to override practically all the HTML output at the template level without modifying the original code. Views and custom components are no exception. Let's test a view override. This will be override for our Malls view and it's going to remove the descriptions in the links that are currently on there and just replace them with links and paragraph tags.