We currently handle a well separated monolithic service which handles various 'contexts' to help with the separation. I haven't had any issues so far when dealing with problems that require the creation of a new context since it was simple enough.
Now I'm dealing with a group of entities (3, to be exact) that relate to each other and I'm not sure how to properly organize one of them in the project.
For the example we'll name them Branch, BranchService, Service.
Branch lives in its own context as does Service, but at the moment I am not sure where to place BranchService. In this case, BranchService is not just an entity to handle many-to-many, it has some information on it's own that is used around the service.
Since they are relatively coupled, should they be together and share the same context? Or is there an alternative for this case?