Changing Yota
architecture with
Tarantool-based cache

Behind the cache in Yota, there is an extensive IT landscape with roughly 200 services. The services are divided into IT products, each in its own isolated infrastructure. For example, the IT product responsible for customer data and the IT product responsible for subscriber notifications work independently. Domains are configured in the cache, so there is no need to send a GET request to a product every time to collect information. The Yota team also added branching logic for domain invalidation. When a backend event occurs—for example, the subscription time runs out—the cache wrapper intercepts the event and resets this particular subscriber’s domain.

Today, Yota has the following services implemented on Tarantool technologies.

The primary Tarantool-based service in Yota is the Profile Aggregation Service‑a personalized cache that speeds up customer data handling. The service collects and caches profile data from adjoining systems. It invalidates the data after receiving external signals. Adding a new profile only requires a configuration.

The domain-oriented Enterprise Persistent Storage holds data structures created by IT products. The service handles saving, updating, reading, and deleting data. For example, it enables the user to create a payment template in the mobile application.

The Semaphore Service stores information about blocked actions in the system. The service is actively used for designing product logic and asynchronous interactions.

The interactive directory was migrated to Tarantool. It stores directories of client numbers ported to Yota as well as region codes. It is synchronized with the Central Database of ported numbers and updates the data every day. The directory quickly provides information to the mobile app, website, and backend.

The product catalog was also migrated to Tarantool. Previously, the configuration required a lot of effort and developer contribution; now an analyst creates a YAML file with the catalog configuration. The new architecture allowed creating a flexible Yota constructor where a customer can choose the number of minutes and gigabytes in a package. With the legacy architecture, this would be technically impossible. Yota’s service catalog structure is defined by YAML.

Frontends Auth Storage Service (FASS) is an authorization service that manages subscriber tokens.