Only RK

Price: 0

Number of applications: 1

Decision acceptance deadline

10.12.25 (inclusive)

Form of award

monetary

Product status

MVP

Task type

ICT tasks

Сфера применения

Media sphere

Область задачи

IT

Type of product

Mobile app

Problem description

The CAP theorem for distributed storage states that in conditions of possible network partitions, it is impossible to simultaneously guarantee both strict consistency and full availability. If the connection between the nodes is broken, you have to choose: either block operations for the sake of consistency, or continue accepting requests at the cost of time differences. The customer's requirement does not allow for either, that is, it goes beyond the provably achievable. The Fisher–Lynch–Paterson result shows that in a fully asynchronous system with the possibility of failure of at least one node, there is no deterministic consensus algorithm that simultaneously guarantees security and survivability. In other words, with an unfavorable message schedule, the algorithm can "fluctuate" indefinitely without reaching a solution. The customer's requirement essentially prescribes the impossible: to ensure guaranteed and prompt decision-making in all possible network scenarios.

Expected effect

The task of "making sure that in case of any network failures and partitions, global storage remains both strictly consistent and always accessible, while meeting a strict latency limit" theoretically has no general solution. Real systems are forced to choose a compromise: sacrifice part of accessibility, weaken the consistency model, or abandon global consensus in favor of local solutions.

Full name of responsible person

Sergeev I.A.

Purpose and description of task (project)

The customer maintains a global service with users in different regions. The infrastructure consists of several data centers and a cluster of databases that mobile applications rely on. Strict requirement: any record (for example, debiting funds or changing a critical status) must be confirmed within <50 ms ** from anywhere in the world**, while: • data is always strictly consistent (sequential reads see the same general order of operations); • The system is always available (no "try again later" errors); • Failure of a separate node or network separation should not lead to a shutdown. Such a set of requirements directly collides with the well‑known limitations of the CAP theorem and the results of FLP.

Note