The purpose of this epic is to create a centralized view of priorities for ~"team::Scalability-Practices" This epic should be considered the single source of truth of the team's roadmap. https://docs.google.com/spreadsheets/d/1xnvDBqZ4ADljvE1IPlqQ6ERcYNjnbSwztRIsFdx8W7o/edit#gid=132675354 **Product DRI: @swiskow** **EM: @kwanyangu** ## Boards By status: https://gitlab.com/groups/gitlab-com/gl-infra/-/epic_boards/1059762?not[label_name][]=roadmap&label_name[]=team%3A%3AScalability-Practices By category: https://gitlab.com/groups/gitlab-com/gl-infra/-/epic_boards/1061628?not[label_name][]=workflow-infra%3A%3ABacklog&not[label_name][]=roadmap&label_name[]=team%3A%3AScalability-Practices ## Strategy Our Roadmap is informed by our [group direction and strategy](https://about.gitlab.com/direction/saas-platforms/scalability/) as well as our [team direction](https://about.gitlab.com/direction/saas-platforms/scalability/practices/). ### Runway Practices also manages Runway. For Runway specific items, please see https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/969+ ## Now Please refer to &148, which we use to track the in-progress epics for ~"group::scalability" and Grand Review. - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1386+ - Counterpart: Product Analytics - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/3727+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/3718+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1395+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/3739+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1352+ - https://gitlab.com/groups/gitlab-com/gl-infra/platform/runway/-/epics/4+ - https://gitlab.com/groups/gitlab-com/gl-infra/platform/runway/-/epics/7+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1332+ ## Next - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/3418+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2789+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1395+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2155+ - https://gitlab.com/groups/gitlab-org/-/epics/9412+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/3560+ - Redis Deployment Guidelines - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1367+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1312+ - Runners Deployments / Scaling (migrating to GRIT) https://gitlab.com/groups/gitlab-org/ci-cd/runner-tools/-/epics/1+ ## Later - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1366+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1324+ - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2740+ - Revamp Runbooks - https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2739+ - Zero downtime deployments - Health checks migrations - Ansible auto-rollback on error ## Wishlist - Sort services and their current Paved road - Paved roads are listed: Core, Monolith, Runway, Independent - New Counterpart model - Practices Entrypoint Defined and documented - Define a Well-Architected framework - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1350+ - Redis is a well-architected service - Sidekiq is a well-architected service - Align the Readiness Review process with a Well-Architected framework - Engineering Portal Provides Service Ownership - Engineering Portal pilot - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1207+ - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1272+ - Define the Independent path - Define the Monolith path - Define the Runway path - Define the Core path - Paved Roads and Dedicated - Runway's Impact on Production Readiness - Integrate Service Maturity Model to Well architected framework - Align the Readiness Review process with a Well-Architected framework - All services have a health scorecard - Engineering Portal GA - Engineering Portal provides services and features metrics and insights