Steamhaus is hugely experienced with designing and building very high traffic architectures, so we used a combination of that experience, performance testing, and the latest developments in the AWS platform and Magento to settle on a design that not only scaled, but offered business agility.
As well as engaging Steamhaus in this migration project, Regatta engaged a new Magento development partner. We began discussions with all three parties to gather requirements and understand the separation of responsibilities—and the touch points between. Perfect communication is key at this stage of a project.
With a limited level of access to the existing infrastructure, we spent a number of days reverse engineering the existing AWS account and Magento deployment. We then began identifying specific tasks which were sized, prioritised, and added to our Kanban management system backlog.
Regatta’s Magento implementation, like most, places very high network traffic demands on Redis for configuration caching. Taking advantage of some of the developments in the latest version of Magento 2 Enterprise, Steamhaus were able to horizontally scale Redis read traffic across many nodes within an Elasticache Relication Group, resulting in higher performance and better cost efficiency.
As well as end user and regression testing undertaken by Regatta, Steamhaus wrote a performance testing suite using Locust. The test suite was executed via many parallel Lambda invocations simulating a high traffic sale. This highlighted a number of stress points which were addressed and retested.