Organizing ownership: How we assign errors in our monolith

The text discusses how incident.io runs on a monolith, which has its own set of advantages such as not worrying about internal network requests speed, complex deployments, or optimizing work that touches multiple services. However, defining ownership in a monolith can be challenging. To address this issue, the author explains how they link their code to the team that owns it, ensuring errors and alerting are routed to the right place with minimal maintenance burden. They divide their codebase into chunks that can sensibly be assigned to a single team, assign ownership to each subfolder in these packages, and encode this information using module files. The author also provides guidance on how to handle fallbacks when no team is assigned.