Case study: Ecommerce

A full fledged magento shop for a famous clothing brand from South India who wanted to revamp their existing site after it crumbled under the immense traffic.




Working model: Outsourced model
Team size: 4
Duration: 3 and a half months
Current status: on support and maintenance.

Problem

During the lockdown there was a surge in site traffic crumbling the servers impacting the page loading time and exposing a lot of bugs. Patching the existing site was becoming a pain as the issues were reported continously and the bounce rate was climbing resulting in business loss.

Solution

A new magento 2 shop on AWS with LB, EC2, Amazon Aurora, EFS and Cloudfare.

How we got it done

The new website was completed in phases as shown below.

Analysing the existing site to identify all the issues, improvements and new additions. This immensely helped with tailoring a solution for the client rather than providing a general solution.

Duration : 1 week. (Google analytics was already present on their existing site)

27 made use of the following tools on the client's existing site during this phase:

  • google analytics for visitor statistics during campaigns and in general
  • google page speed and chrome lighthouse for user experience, performance and SEO score
  • server logs for request-response latency and drops
  • hosting provider tools for inspecting server outage reasons
  • Tools to identify strategies implemented by competitor sites


formulating a robust strategy on all the 3 fronts - Infrastructure, backend and frontend.

Duration : 3 weeks.

The following activities were undertaken during this phase:

  • Strategize the move from magento 1 to 2
  • Data migration strategy from existing site to new site
  • Identifying the various infrastructure elements to mitigate site traffic and page loading time
    - CPU, RAM and Zones
    - Application instances, Load Balancers, EFS and S3
  • Comparing the cost of hosting on various cloud infrastructure
  • Identifying (going through reviews and costs) the various extensions / plugins for Magento 2 to help speed up development
  • Version 1 deliverables
  • Deployment strategy with phased go live (5% traffic to 20% to 100% - based on location)


Scrum methodology to go live in 2 months. Each sprint was a week long and we had 8 sprints.

Duration : 8 weeks.

It was clear that we needed to do the following to be able to go live in 9 weeks:

  • Minimum UI modifications on the theme
  • Reliable plugin for data migration from magento 1 to 2
  • maintain the same UI flow as much as possible on the new site (to make it easy for repeat customers)
  • go with little to no new functionality for first version
  • concentrate more on dealing with site traffic, caching strategies and page / site performance


making sure the go live is smooth with phased approach and is monitored so that new as well as repeat customers seamlessly adapt to the new rollout.

Duration : 1 week.

The following activities where undertaken as part of go live:

  • migration from staging to live
  • implement basic site tracking for post deployment analysis (among other checklists)
  • phased go-live
  • post go live monitoring