Skip to main content

Responsibility Documentation

Context​

Microservices are being adopted. There are multiple microservices, each with exactly one responsible team for it.

Problem​

  • It is challenging to find a contact person when there are questions about a microservices or there is need for coordination

Solution​

Maintain the documentation of responsibilities for each microservice. Include which team is responsible and who serves as a first point of contact if questions arise.

Maturity​

More data required (only 2 sources)

Sources of Evidence​

L45:

  • In context of recovering microservice-based architectures => DSL Metamodel
    • Use repo information of each developer contributing to the repository is collected
    • Metamodel: Microservice owned by exactly one team
  • Tracking people assigned to microservices
    • => detect management issues: e.g. too many devs assigned to one microservice or vice versa

L46:

  • in context of an enterprise-wide shared repository of all microservice specs (for reuse)
  • document ownership as well