Categories : All, Case Study, Retail / E-commerce, Web & Desktop Application
The requirement of the client has been divided into two modules: Site Performance Optimization and OMS (Order Management System). So, let us take a glance at both of them one by one:
Site Performance Optimization:
The Site Performance Optimization is divided into two parts; the first one is the server level configuration change that included the implementing cache and database, web server as well as CDM. Another is the application level configuration change. It also manages the load balancer and My SOL replication. The client wanted to loading time to get decreased at the considerable rate, as it was taking a lot of time to load all the content and images of the page.
OMS stands for the Order Management System which is responsible for managing the entire order flow once the order is received. Once the order is received, the customer should be given the tracking id so that they can keep the track of their product. Then, the products have been allocated to the stores and the picker management should begin. The pickers should be allocated to each store so that they can collect it after checking. Once they collect it, the order should be shipped and delivered on time.
Well, the team faced a few difficulties during the project. So, let us talk about them one by one:
|Operating System||Red Hat Linux OS, Multi-Server Architecture with Environment through Version Controlling releases, Server Optimization, Security & SSL Implementation, Scheduler for Back-ups, Alert Monitoring System Integration, Server Performance Tuning at regular intervals, Software Firewall Configuration &|
|Development Tools & Environments||PHP5+, Magento Enterprise Edition 1.12, Zend Framework, Nginx Web Server,Lucen SOLR – Site search, Redis cache, Load Balancer, New Relic – Monitoring tool, Akamai CDN, AJAX, Java Script, HTML5, CSS3 etc.|
|Database||MYSQL Database Server, DB Clustering, DB Optimization, Master Slave Replication, Query Optimization, Scheduler for Backups.|
All the planning was done keeping in mind the successful and on time delivery to all the customers. So, let us look at the planning steps:
In order to ensure the smooth performance of the system, the team decided to use the MVC architecture in this project:
The reason for choosing the MVC as the architecture is its long list of benefits. It separates the business layer from the user interface making it really clean and extensible which will prove really helpful in the future. Moreover, as it contains so many libraries, it will make your tasks even easier. It serves as a great tool of development, as you can assign modules to various developers and then merge all the modules in the end once all the modules are developed. If you know the framework, it will be really easy for you to develop it too soon and meet the deadlines. In addition to that, it becomes more SEO friendly.
The MVC architecture: