Which SLIs/SLOs are relevant for Monorepos vs polyrepos?

In the context of Monorepos and Polyrepos, various Service Level Indicators (SLIs) and Service Level Objectives (SLOs) become relevant depending on the architecture and deployment strategies of the codebase.

SLIs/SLOs for Monorepos

  • Build Time: Track the time required to build the entire repository.
  • Test Coverage: Measure the percentage of code covered by automated tests across the entire codebase.
  • Deployment Frequency: Monitor how often components are deployed from the monorepo.
  • Change Failure Rate: The percentage of changes that fail to meet quality standards when deployed.

SLIs/SLOs for Polyrepos

  • Individual Repo Build Times: Report on build times for each repository separately.
  • Inter-Repo Dependencies: Measure the health and response time of interactions between different repositories.
  • Deployment Success Rate: Percentage of successful deployments across all repositories.
  • Service Availability: Monitor uptime and responsiveness of services that are part of various repositories.

Monorepos Polyrepos SLIs SLOs DevOps Build Time Test Coverage Deployment Frequency Change Failure Rate Repository Health