This is an umbrella theme spanning all Data Access teams, stated as follows: ensure long-term scalability and maintainability of our infrastructure while serving business needs according to the [FY26 Platforms strategy](https://docs.google.com/document/d/1E5T9TSkqxWkvCpWNbfrqmEFM5sXMO4HT-D22m_QjfyA/edit). ## Goals 1. Become intentional about growth 1. Reduce historical usage 1. Comply with [retention policies](https://gitlab.com/groups/gitlab-org/-/epics/13693) 1. Maintain (or enhance) developer velocity in shipping features -- we still want to enable everyone 1. Minimize related toil ## Data Access teams to do 1. **Measure** key metrics of their data scalability and access patterns, track their changes and relations to breaking points 1. **Attribute** usage to its source (for example, tie growth of a metric or a database query to a given product feature) 1. **Provide** policies defining the "paved paths", ie the good patterns to follow when storing and accessing data, through documentation, consultation, and processes in their scope 1. **Automate** actively detecting and preventing bad patterns from entering GitLab, as early in the development cycle as possible 1. **Measure** the impact of the above, set targets and report on success ## Entry points - https://gitlab.com/groups/gitlab-org/-/epics/14527+ - https://gitlab.com/groups/gitlab-org/-/epics/12961+ - https://gitlab.com/groups/gitlab-org/-/epics/16268+ - https://gitlab.com/groups/gitlab-org/-/epics/16271+ - https://gitlab.com/groups/gitlab-com/gl-infra/data-access/durability/-/epics/13+ - https://gitlab.com/groups/gitlab-com/gl-infra/data-access/durability/-/epics/9+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1410+ - https://gitlab.com/gitlab-org/gitaly/-/issues/6380+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/4069+ - https://gitlab.com/groups/gitlab-com/gl-infra/data-access/durability/-/epics/21+