Server migration: reasons, status, and forecast

Due to sanctions threats and regulatory requirements, KickEX organized the relocation of its servers to Russia, namely the transfer of infrastructure from AWS to Yandex.Cloud. This migration aims to improve the resilience and security of the exchange.

Like any multi-component process, infrastructure migration involves several areas of work, takes time, and entails certain consequences. Thus, due to the migration of large databases, the exchange was forced to temporarily suspend operations — primarily for the safety of customers and their transactions.

Technical specialists have already gone part of the way, namely, they have successfully migrated the most important thing, all databases that occupy terabytes. In the process, it was also possible to carry out additional optimization of some databases, which in the future will have a positive impact on the performance and load stability of the entire ecosystem.

However, because of the Yandex.Cloud and AWS infrastructures differenсe, and it takes a little longer than we planned to resume work in the proper mode: seamless migration was not achieved. Now the team’s IT experts have to manually migrate each service and rewrite configurations that will work in the new environment.

Now employees are working to launch the copied, already working databases for the “live” server, restore docker files for some projects, and fix errors in compiling some of the docker images that arose due to the same difference in server data architectures.

We thank you all for your understanding and patience, and we are doing our best to return to our usual workflow as soon as possible. We will continue to keep you updated and tell you in as much detail as possible what stage of the migration we are in.