|Slack Channels||#g_scalability (Primary Team Channel), #infrastructure-lounge (Infrastructure Group Channel), #incident-management (Incident Management), #alerts-general (SLO alerting), #mech_symp_alerts (Mechanical Sympathy Alerts)|
The Scalability team is responsible for GitLab and GitLab.com at scale, working on the highest priority scalability items in the application in close coordination with Reliability Engineering teams and providing feedback to other Engineering teams so they can become better at scalability as well.
As its name implies, the Scalability team enhances the availability, reliability and, performance of GitLab by observing applications capabilities to operate at GitLab.com scale. The Scalability team analizes application performance on GitLab.com, recognizes bottlenecks in service availability, proposes short term improvements and develops long term plans that help drive the decisions of other Engineering teams.
Short term goals include:
Diagram below describes how the work gets prioritized in the Scalability team:
Process contains 6 cyclical stages:
The work process will be defined when the team is (partially) staffed and working on the first task, to ensure that the process fits the project and the team structure.
The Scalability team will work with all engineering teams across all departments as a representative of GitLab.com as one of the largest GitLab installations, to ensure that GitLab continues to scale in a safe and sustainable way.
The Memory team is a natural counterpart to the Scalability team, but their missions are complementing each other rather than overlap:
The following people are members of the Scalability Team:
|New Vacancy - Marin Jankovski (Interim)||Engineering Manager, Scalability|
|Andrew Newdigate||Distinguished Engineer, Infrastructure|
|Bob Van Landuyt||Senior Backend Engineer, Scalability|
workflowlabels to the issue. The team will triage the issue and apply these.
We celebrate our wins! Whenever a change driven by the Scalability Team shows a clear positive impact on the scalability of GitLab.com; through key metrics, saturation reduction, reduced Mean time to Detection (MTTD), improved Mean time between Failures, etc, we post a message as a comment on this snippet in our tracker: https://gitlab.com/gitlab-com/gl-infra/scalability/snippets/1900609.