Maintaining & Supporting a Large Digital Store on Magento 2

The challenge with this project was to migrate a high-traffic site with large databases to run quickly and securely on Magento 2. Find out how we managed it with zero downtime.

WEBSITE

emanualonline.com

INDUSTRY

Repair Manuals

TEAM

Project Manager, Magento Certified Developers (2)

TRAFFIC

900K Monthly Visits

KEY SERVICES & INTEGRATIONS

Magento 2, Stripe, ActiveCampaign, ShopperApproved, Azure, PayPal

Solution.

1. OsCommerce to Magento 2 migration.

Initially, the store was working in OSCommerce until the founders faced intractable problems with website updating. Then they decided to switch to Magento 2. The platform was a brilliant solution because of its ability to handle big and highly customisable e-commerce stores.

We planned and carried out the Migration for them, mitigating any issues we had foreseen ahead of time.

Additionally, we implemented the new design of the store.

2. Security.

The vast dataset is stored on dedicated and secured servers – we created a separate front-end interface and integrated it with the Magento system. We also helped to configure the server clusters and implemented a zero-downtime-time deployment process.

The store has a target audience spanning all time zones, the traffic of the website is nearly 400К/month, and the daily number of orders is about 600, so this store must remain online at all times.

The devs are top-notch. These guys implemented my website when probably 5-7 other agencies/freelancers failed! You can get Paul on a Zoom/Google Meet call anytime, and he is very open to discussion. If you're not happy with something, he's out there to fix it for you and will make it happen.

Chod Shen-Ina

CEO, EMANUALONLINE

3. ShopperApproved integration.

One of the project requirements was to make the Shopper Approved integration. Usually, we would simply implement the widget on the front-end; however, in this case, we were tasked to reduce the website loading speed, so we suggested adding the server-side integration with daily parsing of reviews and FAQ.

4. Payment gateway and generation of download links.

After a successful transaction, the system needed to show a download link for the user. SalesForce’s real-time integration made this process more cumbersome: each payment was required to be processed via SalesForce. It meant the link would be shown to the user only after the data in SalesForce was created. In general, the user would have to wait 20-30 seconds on checkout before the link is generated.

We overcame this obstacle with the custom SalesForce sync; therefore, we refused the real-time integration favoring the user’s convenience.

All service and marketing emails were transferred to a separate queue to make the entire website work faster.

5. Product feeds for Feedonomics.

As a part of the integration, Feedonomics provided the script for the database sync. For a store having 360,000 items in the inventory, this poses a problem. In our case, the script execution time equaled approximately 9 hours, and it increased server load.

We created a custom script for Feedonomics to use; the execution of the script was reduced to 20 minutes only.