Blueprint: Reduce and limit table sizes on GitLab.com to < 100 GB

This is a proposal to communicate and work on a target for maximum on-disk size per physical table on GitLab.com.

This sets a clear, measurable goal and expectations. It needs to be re-evaluated continuously with GitLab.com growing. For details how this is being applied pragmatically, see the document.

graph LR
    Fe(Pick feature) --> D
    D[(Database)] --> De
    De[Debloating] --> Dc
    Dc[Decomposition] --> P
    P[Partitioning] --> S
    S[Sharding] --> R
    P --> M
    M[Microservices] --> R
    R{Repeat?} --> Fe
    style De fill:#fca326
    style P fill:#fc6d26

Who will drive this work?

groupdatabase to own the following:

1. Work with development to establish this target
2. Monitor growth and situation on GitLab.com
3. Find and propose solutions to reducing the table sizes and document those in detail in issues
4. Work with the stage groups to prioritize and schedule those efforts, or drive solutions to completion where possible

How will we organize work?

I have created &6211 for a proposal with a few examples:

1. One epic per table violating the rule
2. Document proposals and different solutions to reducing the table size in issues on those epics

Nothing there yet - only a showcase how we can organize work.