Team Vision

Vision for the Application Platform

How big is the team, and what are the subteams/squads?

  • Guidance Squad

    • 2-3 engineers, but it can overlap with people in other squads

    • Provide requirements & tools for microservice teams to profile

    • Provisional guidance -> permanent guidance

  • SRE

    • 2 co-leads, + others?

    • ?? on call stuff how???

    • Goals

      • Identify sets of tools

      • Retrospective analysis

  • DevOps

    • 1 lead

    • 2-3 engineers

  • Platform (Terraform + k8s extensions + scaling)

    • 1 lead

    • 2-3 engineers

  • Team Size: 12 people

    • w/ some churn, target 50% turnover every 3 months

    • Ideally 8 people who are long term, plus 8 churn positions

What is the actual scaling expectation for this entire platform?

  • (1) The implied expectation is for a reliable cloud platform, good SLA

  • (2) Efficient support for DevOps

  • (3) CPU and mem loads need to be known and applied to limits & requests

    • Really a performance testing/metrics question

    • Load testing working group

    • Profiling of each service

  • (4) Cloud Burn

How do we expect this team to work long term? Short term?

  • Subteams, with team leads or co-leads

  • Long term, paid SRE position

    • Beginning of 2022, assuming current scale

  • Short term - automated SRE as much as possible

  • Interns ( Guidance squad describes a specific project )

  • More focus on well articulated tasks ahead of task assignment -> Guidance squad

What’s the technology vision?

  • Build before buy, open source - what does this imply?

  • What is unique about the nature of this approach/team?

  • Culture -> Guidance Team

  • Outreach

    • Interface with experts on certain platforms

    • Should we join open source communities ourselves

      • Can we promote our team there somehow

    • Developer advocates

    • Universities (advertising to students, or other avenues like class projects)

    • Attending Conferences

  • What happens at large, global, internet scale

    • Are we going to be AWS - that’s not practical

    • Partner with other open source companies

      • Or just with other mid-sized companies

    • We are gonna think this through when we get there

      • But, we’ll try to stay true to our open source values and ecosystem

What can we scale?

What kind of scale questions/needs do other teams have?

Questionnaire for other teams/other team leads

  • Things teams might want to do as they scale

    • Performance testing

  • Things teams might need to do was they face scale issues

  • What services are valuable to provide to volunteers so they can efficiently contribute?

  • Frameworks for teams

Team sourcing

  • Volunteers sourcing volunteers (friends, coworkers, linkedin, etc)

  • Companies getting involved

  • Other open source groups

  • Advocacy

  • Speakers, blog posts, etc

Last updated