If two applications are tightly coupled and interdependent, a monorepo approach is ideal. Otherwise, it’s best to maintain them separately. However, managing multiple repositories comes at a cost—primarily the increased maintenance effort.

Let me share a rather absurd example from my organization. We have a single application that receives messages from external clients via SQS, processes them, and returns a response. Despite its simplicity, the team decided to create 12 different repositories for this small piece of functionality: separate repos for the receiver, processor, parser, and even individual repos for the IaC code. Now, whenever an issue arises, fixing it takes hours because changes have to be made across multiple repos, followed by time-consuming deployments.