Magento Store Setup
- Magento - Setup Store Live
- Magento - Setup Google Checkout
- Magento - Setup Paypal Payment
- Magento - Setup Check Out Options
- Magento - Setup Currencies
- Magento - Setup Payment Methods
- Magento - Setup Payment Gateway
- Magento - Setup Payment Plans
- Magento - Setup Shipping Rates
- Magento - Setup Taxes
- Magento - Setup Inventory
- Magento - Setup Products
- Magento - Setup Categories
- Magento - Setup Contact
- Magento - Setup Languages
- Magento - Product Overview
Magento Order Processing
- Magento - Manage Orders
- Magento - Create Orders
- Magento - Setup Order Emails
- Magento - Setup Order Options
- Magento - Orders Life Cycle
Magento System Setup
- Magento - Setup Newsletter
- Magento - Setup CMS
- Magento - Setup New Pages
- Magento - Setup Page Layout
- Magento - Setup Page Title
- Magento - Setup System Theme
- Magento - Setup Translation
- Magento - Setup Facebook Likes
- Magento - Setup Youtube Video
- Magento - Setup Pretty URLs
- Magento - Setup Google Analytics
- Magento - Setup Customers
Magento Optimization
- Search Engine Optimization
- Magento - Database Performance
- Magento - Profiling
- Magento - Site Optimization
Magento Useful Resources
- Magento - Discussion
- Magento - Useful Resources
- Magento - Quick Guide
- Magento - Questions and Answers
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Magento - Architecture
In this chapter, we are going to discuss the architectural style of Magento, for implementing user interfaces. The following diagram shows the architecture of Magento −
The Magento architecture comes with Models, Views and Controllers.
User Request − The user sends a request to a server in the form of request message where web browsers, search engines, etc. act pke cpents.
View − View represents the data in particular format. It is the user interface which is responsible for displaying the response for user request. It specifies an idea behind the presentation of the model s data to the user. Views are used to reflect "how your data should look pke".
Controller − The controller is responsible for responding to user input and perform interactions on the data model objects. It uses models to process the data and send responses back to the view.
Model − The model is responsible for managing the data of the apppcation. It contains logic of the data and represents basic data object in the framework. It responds to request from the view and to the instructions from the controller to update itself.
Database − Database contains the information which is requested from the user. When the user requests data, view sends requests to the controller, the controller requests from the model and the model fetches the required information from the database and responds to the user.
WSDL − WSDL stands for Web Services Description Language. It is used for describing web services and how to access them.