Friday, October 22, 2021
In our new series "The Developer's Diary" we give you an insight into the everyday life of our colleagues. From now on, they will report at regular intervals on updates, but also on successes and challenges in their projects. There are also interesting technological and methodological insights.
After explaining the conditions of our project at Carrera in the last article, today we dive deep into the current status and challenges of the team.
The project is currently in the phase of conceptualising and replacing the existing backend. The focus of the past weeks has also been on the internationalisation of the shop and its performance.
An important point in this project phase was the languages in the shop. These were previously maintained in the CMS. However, problems often arose here, especially when creating new languages and corresponding keys. To counteract this, the byte5 team used a new toolset: i18nexus. It is a kind of dashboard for translations. i18nexus simplifies their creation, for example through automatic generation, but also through separate systems for content managers. Content managers only have access to the parts of the shop system that are relevant to them. Since content in the Carrera shop is played out on the server, the translated pages are not loaded dynamically, but are provided statically. Through specially adapted mechanisms, we can deliver all languages and all e-commerce processes with high performance.
Speaking of performance: speed was also on the byte5 team's to-do list.
As a user, it is no fun to use a shop that takes forever to load. Before our optimisation, you always waited several seconds for the backend to react. Now the individual pages are pre-built and delivered, which brings an enormous increase in speed in comparison. The most beautiful shop is of no use if it is slow.Laurens Bergmann, Developer
The integrated PIM system has also decoupled and reduced the size of process chains, which also leads to increased speed and higher performance. Whereas previously several systems interlocked, the frontend now only addresses the PIM, which communicates with the ERP system in a new process (see graphic). As a result, several requests can be made asynchronously and the processes can be accelerated enormously.
Decoupling and downsizing of process chains for increased speed and higher performance. - © byte5
The improved performance was actually planned for a later project phase. However, since this laid the foundation for further optimisations, this step was brought forward.
Currently, the focus is on the backend. Jure and Marlon have already started building it. I am now linking the new backend with the current frontend piece by piece.Laurens Bergmann, Entwicklung
We expect this phase to be completed in about two weeks. However, a hybrid solution for a single shop page is already live and being run from the new backend. This makes it possible to really deliver individual components as they are desired, to provide all the required information and at the same time to achieve faster response times. This is followed by the migration of all customer and product data from the old backend to the new one.
Seamless migration is indeed still a topic we all have respect for. At the moment, we are looking at different alternatives to handle the migration as cleverly as possible.Marcel Wege, CTO & Team Leader
We know from our many years of experience how important data migration is for the success of the project. This makes it easy for our colleagues to put themselves in the customer's shoes and think through all the necessary steps.