Improved Rostelecom personal account architecture built with Tarantool
cover

Improved Rostelecom
personal account
architecture built with
Tarantool

Scroll

What is Rostelecom?


Rostelecom is one of the largest providers of digital services and solutions in Russia. It provides a personal account for clients to manage, connect, and pay for the services. As the load on the personal account increased, it became necessary to build a new microservice-based architecture to make new feature development more flexible.



Another objective was to switch to the Russian technology stack as part of the import substitution program. After considering several possible solutions, Rostelecom settled on Tarantool.

Task and requirements

The Rostelecom personal account service has millions of active subscribers. Before switching to Tarantool, the service worked on Oracle for 10 years.

The company needed to:

  • Migrate to Russian software (products included in the register of the Ministry of Digital Development were considered as the first priority)
  • Build a new architecture and switch from a monolith to microservices to make it easier to work with Kubernetes and integrate parallel development

As a part of the personal account refactoring, the provider was looking for an in-memory database solution to store sessions and user authorization data. Redis was not a viable option as it doesn’t have vendor support in Russia, which was a vital point for the provider’s team. Personal account is a critical service, therefore swift vendor support is necessary in case of failure. A situation in which subscribers cannot log into their account and use a service is unacceptable.

After analyzing a number of options, the Rostelecom team chose Tarantool.

Why Tarantool:

  • Client help and in-depth consultations even before switching to the paid version
  • 24/7 technical support
  • Compatibility with the RED OS operating system
  • Tarantool is included in the register of the Ministry of Digital Development
  • Tools for automated deployment for test and production environments
  • The expirationd data cleaning module
  • Solution by a domestic company

Solution

Monitoring and support

Solution

icon

Before Tarantool was adopted, Rostelecom developers made a working prototype of the new architecture based on the Community Edition version. However, it had certain deployment limitations. That’s why the developers turned to a Tarantool team consisting of core developers, implementation experts, architects, and a project manager. The Rostelecom team participated in a number of webinars where they were given an overview of Tarantool and its features. After developing the architecture and topology of the solution, the Rostelecom specialists came to the conclusion that they needed the Enterprise Edition version of Tarantool.

At the time of the discussion, Tarantool was working on a new product — a boxed NoSQL database Tarantool DB. It was ideal for Rostelecom because it included a ready-made set of application modules and features.

Monitoring and support

icon

After Rostelecom deployed the infrastructure, Tarantool specialists continued to support the team. During load tests, a specialist from Tarantool was also in contact for consultation and support. Tarantool also helped with updates and transition to new versions of the product, which included frameworks for Spring Boot. Now all updates are carried out automatically.

Tarantool specialists also helped with monitoring setup. In addition to a large number of built-in monitoring tools, Tarantool has ready-made dashboards for Grafana that do not require modifications and work out of the box. This allowed the Rostelecom team to quickly set up monitoring of servers, including the production environment.

icon icon
Scroll

Results

The transition of the personal account service to Tarantool took place during the New Year holidays. It went quite smoothly: the team closely monitored user requests and did not notice any negative feedback or reports of difficulties. This was an important point for the provider — the service with a multi-million audience remained available for everyone.

1 000 000

Migrating cache of millions of sessions From the business perspective, seamless migration is invaluable for an operating service. During the personal account migration, all user data was saved and no serious incidents occurred.

Migration

Migration to a Russian solution Full support from Tarantool.

Transition

Transition to a microservice architecture Convenient work with Kubernetes.

Customer Quote

For the Rostelecom team, this was the first experience in implementing in-memory databases on such a large scale. After migrating to Tarantool, we received tools for further development of projects and new solutions to provide service for our users. Such migration is a critical step, as it affects all Rostelecom users. On our end, Tarantool’s operation is supported by a team of DevOps engineers, and we receive prompt responses from the Tarantool team to any questions that arise.

Ruslan Tagirov

Head of the Development Infrastructure Department, Digital Project Development Competence Center, Regional Development Center in Yekaterinburg.

The personal account is used by clients of home Internet, mobile communications, and other Rostelecom services. There are up to 270 million transactions carried out per month, and their number is constantly growing, while user interest in remote service and self-service is increasing. As a result of the implemented changes, the personal account is now faster and more stable. The number of transactions per client increased by 32%, and the number of active users of the application increased by almost 10%.

Evgeny Zhukovich

Customer Service Director at Rostelecom.

Get a consultation

Request a demo

Thank you for your request

Tarantool experts will
contact you shortly