They also adopted a policy of ensuring that their DB changes are backwards-compatible to prevent issues. This means that for their own module updates, they can trigger their own migrations, and only need to use maintenance pages for Magento migrations. Phinx is a platform-independent database migration library that they were able to use via a Magento module to improve the downtime. Inviqa were able to parallelise the import in order to vastly reduce the time involved in the import process – an 850% improvement in response times, and a 600% improvement in product creation times.ĭatabase upgrades were the major issue in achieving zero-downtime, and the general solution from the community was to use maintenance pages, but maintenance pages mean downtime and toom didn’t want any downtime. Toom uses a PIM to control their production information, utilising middleware to import it to their channels (such as Magento) but at 3 seconds per product creation, it would have taken 5 days to import all of their products.
#Magento2 devdocs bluefoot full#
They were also able to utilise MView to perform partial index updates rather than full index updates to speed up indexing. They were able to address this by using unbuffered queries, but this has its own issues which needed to be dealt with. The indexes contain 35 million stock items and 17 million prices – the query results involved were simply too big for PHP to handle. The existing microservices were able to be utilised to populate the new models. Inviqa also added custom price and stock indexes to increase performance. Magento 2’s dependency injection allowed them to simply replace the Magento stock and price models with their own models. After consultation with Magento, they created a custom market model which also led to setting up the required custom stock and price models, allowing toom to have different prices and stock levels for each physical store. To model their 350 stores, they considered using the Magento store models but it massively increased the load time and indexes and made the website unusable. With a product management system, a content management system, and a careers system to be integrated, they faced issues with distributed architecture which was resolved using Varnish to handle routing and using Varnish ESI to assemble pages. Toom is a large company in Germany with over 350 physical stores that needed to be adapted to a Magento framework. James Halsall, Technical Team Lead, Inviqa Session: toom + Magento: A Journey to Zero-DowntimeĬhristian Dornhoff, Head of IT (Cross-Channel), toom It is a set of tools and technologies which can bring native app functionality to your website across all devices, not just mobile. Implementing a PWA isn’t a silver bullet on its own. While many amazing features of PWA are available, the real low hanging fruit is to improve the front end performance of the site. We are only just beginning to see what is possible with PWAs. PWAs are the next paradigm shift for the web. Speakers: Shane Osbourne, Frontend Web Developer, JH Day 2 of Magento Live Europe is well underway….find out more about the sessions our team is attending today or click the link below to skip to:
0 kommentar(er)
