Sharding: Amplifying SaaS Reliability Focus for Q3FY22
This is the Sharding-specific issue for #2881 (closed). The purpose is to provide a tracking and organization issue for surfacing the critical customer needs and opportunities to improve SaaS reliability for each group. Once collected, we can surface this back up to the main parent issue in a clear way.
Asks
See: #2881 (closed)
- PM: Understand and share what are the minimal-must-do features/capabilities we should deliver to meet customer ARR commitments from 14.2 through 14.6
- EM: Understand and share What are the top most things you could advocate for to improve reliability of your areas. In addition to improving reliability, consider observability needs to detect and fix reliability issues when they do occur in SaaS
Discussion
For Sharding I think this is relatively straight-forward, as we are already focusing 100% on SaaS Reliability.
- Decomposing the main GitLab database: gitlab-org&6168 (closed)